rsbuild-v2-upgrade

Migrating to Rsbuild v2 involves updating @rsbuild/core and plugins to v2-compatible versions, adjusting rsbuild.config.* options, and validating with builds and tests. Start by scanning your project structure, review your package.json and config file, then follow the guided upgrade flow to apply v2 changes automatically.

Rsbuild v2 introduces config option changes from v1. The upgrade process identifies and updates your rsbuild.config.ts, rsbuild.config.js, and related files to align with v2 requirements, including plugin configuration updates and deprecated option removals.

Yes. The upgrade flow handles both @rsbuild/core and plugin package versions simultaneously, identifying which plugins need v2 updates and applying version bumps automatically to maintain compatibility across your build setup.

Validation runs automated builds and test suites in local workflows and CI pipelines to confirm the upgrade completed successfully. If builds pass and tests run without errors, your v1-to-v2 migration is complete and your project is ready for v2.

Yes. The upgrade process applies to both local development workflows and CI pipelines with varied plugin configurations, ensuring your migration strategy works regardless of where you run it.

The upgrade identifies custom and third-party plugins in your setup and updates them to v2-compatible versions where available. You may need to review plugin documentation for breaking changes specific to your custom implementations.