fix: classify npm workspace-owned dependencies as direct when scanning from the monorepo root#258
Merged
sonukapoor merged 2 commits intomainfrom Apr 29, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes npm workspace root scans so direct-vs-transitive classification includes dependencies declared in child workspaces, not just the root
package.json.The change reads workspace patterns from the root manifest, resolves workspace folders such as
client,server, andpackages/*, and merges dependency names from each workspacepackage.jsoninto the direct dependency set. Workspace folders without apackage.jsonare ignored.This keeps normal root-lockfile workspace scans honest: dependencies owned directly by a child workspace are no longer mislabeled as transitive solely because they are absent from the root manifest.
Closes #257