fix(query): support package-lock-only in workspaces #8836
Merged
+163
−12
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
ff49871 to
c1c991c
Compare
owlstronaut
reviewed
Dec 8, 2025
01a3857 to
c1c991c
Compare
10ab85e to
3b5f211
Compare
eb6ca8f to
4f3a787
Compare
owlstronaut
approved these changes
Dec 8, 2025
Contributor
owlstronaut
left a comment
There was a problem hiding this comment.
Thank you for addressing the feedback and contributing a fix!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why/What
This change fixes a bug in npm query so that
--package-lock-onlynow works correctly with workspaces, by properly loading the dependency tree from the lockfile instead of node_modules.References
Related to #6732 (comment)