Update to use exact versions of the npm packages & demote npm packages to versions published before 1/11/2025 #261
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request standardizes dependency versioning across the repository by replacing caret (
^) and tilde (~) ranges with exact version numbers in allpackage.jsonfiles. It also updates peer dependencies to require specific versions instead of version ranges, and aligns workspace references to use theworkspace:*syntax. These changes help ensure consistent builds and reduce the risk of unexpected issues due to automatic minor/patch upgrades.Dependency version standardization:
package.jsonfiles now use exact version numbers for dependencies and devDependencies, replacing any caret (^) or tilde (~) ranges. This affects core packages, framework integrations, and sample projects. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16]Peer dependency alignment:
react,react-router,tanstack-router,nextjs,vue, etc.) are updated to require specific major versions instead of loose ranges, improving compatibility and predictability. [1] [2] [3] [4] [5] [6]Workspace reference consistency:
workspace:*syntax for consistency across packages. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]Sample project updates:
samples/__legacy__are updated to use exact dependency versions, matching the main repo’s versioning strategy. [1] [2]VM Build Result

Related Issues
Related PRs
Checklist
Security checks