😅 TIL: https://t.co/ZP4NTmL0cH

🎉 Next.js with Rspack just hit 99% test coverage in development! Experience it now: https://t.co/Cn6qJ1Bp1g

Rspack v1.5 will introduce an experimental optimization that skips building unused reexports in side-effect-free barrel files. This reduces the build time of `import { Button } from 'antd'` from 528ms to 82ms.

BTW I have an article that was written 2 years ago and published externally a few months ago. It primarily focuses on the practical aspects of bundling RSC in webpack. Though some parts may be outdated and need some knowledge about webpack to comprehend. https://t.co/byyXhS49yg

Just finished reading. So excellent article that elaborates on the advantages of RSC from "how to improve loading the bundles" perspective, some of which I wasn't even aware of before.

👀 Next.js experimental MCP server Tools can query module graphs and reported route issues Available in v15.4.2-canary.16

Wrote an article about how React Server Components integrate with a bundler. It's a deep dive into how code splitting works, how RSCs eliminate network waterfalls, how environment directives like "use client" work, CSS loading, etc. Check it out!

👀 https://t.co/72K1qGRQDC

🫶

I believe this makes Parcel the first standalone bundler with built-in RSC support. Unlike other RSC implementations, Parcel is not a framework. It gives you tools to build your own application or framework, experiment with new patterns, or integrate RSCs into an existing app.

Let's get acquainted: 🐈‍⬛ Lynx: Empower the web community and invite more to build across platforms. ⚛️ ReactLynx: Idiomatic React on Lynx. 🦀 Rspeedy: Rspack-based build tool for Lynx. 🦀 https://t.co/kl40ywxccV: Lynx website based on Rspress.

@AndaristRake @acemarke @mweststrate @RollupJS @jaredpalmer @mdiordiev The semantics of the sideEffects flag is the following: A side-effect-free marked modules may be omitted if none of its direct! exports is used. It must not be omitted if any of its direct! exports is used. It does not! flag top-level code in a module as side-effect-free.

optimization.splitChunks.chunks: "all" is the only option you need for vendor and commons splitting in webpack. Best combine it with html-webpack-plugin or equivalent html generation.

I have discovered some truly excellent materials about bundler and am studying them 🧐 https://t.co/NII0rVKXJ6

Dynamic imports were designed wrong, they should have been always statically analyzable at the cost of convenience. It would've been good for both browsers and tools We could still go back and fix it and just ban dynamic imports. This could also work for things like new Worker()

Uploaded my talk on the past, present, and future of bundlers. It covers a bit of history, why we use bundlers, how they work, features like code splitting and tree shaking, and a bit on the evolution and future of JavaScript tooling. Check it out! 📺 https://t.co/Oy2vPTxEbD

Announcing Rspack 1.0 - the next generation JavaScript bundler written in Rust, webpack compatible, 10x faster. Check out the release blog for more details: https://t.co/nOVJjKMRBo

You might think it's a joke (and it partly is to make you have to pull this repo onto your work PC), but watch this space. This is going to be the distributed RSC architecture:

Introducing Fog of War 😶‍🌫️ This new API allows your app to scale to any number of routes without incurring a performance hit on initial load Learn all about it in our latest blog post https://t.co/RPTeNm3k6c

https://t.co/q6y9z55fXs