Skip to content

fix: Node package dependencies ending up as related dependency of the wrong version of the package#5479

Merged
aikebah merged 1 commit intomainfrom
issue-5477
Feb 19, 2023
Merged

fix: Node package dependencies ending up as related dependency of the wrong version of the package#5479
aikebah merged 1 commit intomainfrom
issue-5477

Conversation

@aikebah
Copy link
Copy Markdown
Collaborator

@aikebah aikebah commented Feb 19, 2023

Fixes Issue #5477

Description of Change

Fix-up location determination of the base folder for package.json so that when multiple versions of a package are in the node_modules tree the versions that differ from the version in the root get associated with the appropriate version (which is in the private node_modules folder of their parent)

Have test cases been added to cover the new functionality?

no, locally tested with npm v6, v8 and v9 (package-lock versions 1, 2 and 3) using the reference package.json of the issue in a gradle project.

@boring-cyborg boring-cyborg Bot added the core changes to core label Feb 19, 2023
@jeremylong jeremylong added this to the 8.1.1 milestone Feb 19, 2023
@aikebah aikebah merged commit f857d6d into main Feb 19, 2023
@jeremylong jeremylong deleted the issue-5477 branch February 27, 2023 13:37
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Dec 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

core changes to core

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Node package dependencies ending up as related dependency of the wrong version of the package

2 participants