Rsdoctor often pins Rsbuild/Rspack dependencies, leading to misalignment with the Rstack ecosystem

[tmkx]

Version

N/A

Details

I regularly upgrade and audit project dependencies, and I often find that Rsdoctor pins the Rstack version, which makes it inconsistent with other dependency versions. I’d like to ask whether this is intentional. Is it possible to keep the same pace with the entire ecosystem? 🙏 @chenjiahan

e.g.

rsdoctor/pnpm-workspace.yaml

Lines 16 to 28 in f87b0d3

	'@rsbuild/core': 2.0.9
	'@rsbuild/plugin-check-syntax': 1.6.1
	'@rsbuild/plugin-less': 1.6.4
	'@rsbuild/plugin-node-polyfill': ^1.4.5
	'@rsbuild/plugin-react': 2.0.1
	'@rsbuild/plugin-sass': ^1.5.3
	'@rsbuild/plugin-svgr': 2.0.3
	'@rsbuild/plugin-type-check': ^1.3.5
	'@rslint/core': ^0.5.3
	'@rspack/cli': 2.0.5
	'@rspack/core': 2.0.5
	'@rspack/plugin-react-refresh': 2.0.1
	'@rspack/resolver': 0.2.8

Reproduce link

N/A

Reproduce Steps

N/A

[chenjiahan]

I agree that Rsdoctor should not pin Rsbuild or Rspack dependencies, @yifancong can we fix it?

[yifancong]

OK, I agree that Rsdoctor should avoid pinning Rsbuild/Rspack ecosystem dependencies unnecessarily. I'll update the relevant catalog entries to use compatible semver ranges where appropriate.

[tmkx]

changes to the corporate internal version would also be helpful. thanks for your quick response and support! ❤️