Canary peer dependency of @rspack/core

[maxyasoon]

I am not sure if it is a bug or not. I was just wondering why we are using "@rspack/core": "0.5.9-canary-8778e17-20240403045016" inside the package.json?

As it triggers the following peer dependency warnings on installation for me:

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: @rspack/[email protected]
npm WARN node_modules/@rsbuild/core/node_modules/@rspack/core
npm WARN   @rspack/core@"0.5.9-canary-8778e17-20240403045016" from @rsbuild/[email protected]
npm WARN   node_modules/@rsbuild/core
npm WARN     dev @rsbuild/core@"0.5.7" from the root project
npm WARN     3 more (@rsbuild/plugin-node-polyfill, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peerOptional @rspack/core@"0.x || 1.x" from [email protected]
npm WARN node_modules/@rsbuild/core/node_modules/html-webpack-plugin
npm WARN   html-webpack-plugin@"npm:[email protected]" from @rsbuild/[email protected]
npm WARN   node_modules/@rsbuild/core
npm WARN 
npm WARN Conflicting peer dependency: @rspack/[email protected]
npm WARN node_modules/@rspack/core
npm WARN   peerOptional @rspack/core@"0.x || 1.x" from [email protected]
npm WARN   node_modules/@rsbuild/core/node_modules/html-webpack-plugin
npm WARN     html-webpack-plugin@"npm:[email protected]" from @rsbuild/[email protected]
npm WARN     node_modules/@rsbuild/core

[chenjiahan]

Currently Rsbuild uses the canary version of Rspack to fix some bugs. We will switch back to a stable version when Rspack releases the new version.