fix(core): handle external node without default version when generating a pnpm pruned lockfile #31503
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ng a pnpm pruned lockfile
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
View your CI Pipeline Execution ↗ for commit 02d82e2.
☁️ Nx Cloud last updated this comment at |
FrozenPandaz
approved these changes
Jun 9, 2025
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Current Behavior
When generating a pruned pnpm lockfile, if there's no external node with a default version for a given package and the dependency specification for the package includes a Semver range specifier, an error is thrown.
Expected Behavior
When generating a pruned pnpm lockfile, the parser should correctly handle the scenario where there's no external node with a default version for a given package, and the dependency specification for the package includes a Semver range specifier.
Related Issue(s)
Fixes #28627