The dependency-reduction numbers are the part that stood out to me more than the perf figures. Going from 192 to 1 in @rspack/dev-server and from 15 MB to 1.4 MB of install size is a shift in philosophy, not just a benchmark. Bundling dependencies into the npm package to control transitive versions is also a stronger supply-chain stance than most bundlers take at this stage.

Reading through the list of projects that already ship Rspack (Next.js, Nuxt, Docusaurus, Storybook, Nx, Angular Rspack, and so on), that's also the group most exposed to any 2.0 breakage. The Upgrade Guide and the migration Agent Skill are both listed in the post, which is further than most major-version releases go, but neither of those tells me which of those downstream integrations will need their own updates to stay working against 2.0 defaults. Is there a plan to publish a compatibility matrix for the listed ecosystem integrations as they adopt 2.0, or is that expected to surface through the individual projects' issue trackers?

Rspack is great, I’m using it since 2 years already for all of my projects. Things I would like to see improved:

- programmatic API, especially when it comes about extracting build errors

- more modern way of configuration: currently the config is mostly webpack-compatible which I find always confusing