You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a new Nx workspace from scratch, the package.json dependencies use version modifiers (e.g., ~ or ^). However, when migrating an older Nx workspace to a newer version, the package.json dependencies are pinned to specific versions (without version modifiers), which creates inconsistencies.
Current Behavior
When creating a new Nx workspace from scratch, the
package.json
dependencies use version modifiers (e.g.,~
or^
). However, when migrating an older Nx workspace to a newer version, thepackage.json
dependencies are pinned to specific versions (without version modifiers), which creates inconsistencies.For example:
Expected Behavior
Using version modifiers aligns more with the expected behavior of dependency management in modern JavaScript ecosystems.
GitHub Repo
No response
Steps to Reproduce
npx [email protected] --preset=angular-monorepo
~19.1.0
) in the package.jsonnx migrate latest
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: