Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore extraneous, missing npm dependencies #347

Merged
merged 1 commit into from
Mar 29, 2021
Merged

Conversation

jonabc
Copy link
Contributor

@jonabc jonabc commented Mar 29, 2021

I saw this in a project where two versions of react would have been installed based on direct and indirect dependency requirements. npm decided to only install one while labelling the other as both "extraneous" and "missing". I'm not sure if there is more to this story but I think generally this is a case that would make sense to ignore as not installed in a project.

I tried to find a package that I could use to test this but had a hard time of it, but for some minimal verification I was able to build and run this change locally to verify it fixed the issue I was seeing in my project.

@jonabc jonabc merged commit 940205b into master Mar 29, 2021
@jonabc jonabc deleted the npm-extranous-missing branch March 29, 2021 21:36
jonabc added a commit that referenced this pull request Mar 29, 2021
## 2.15.0

2021-03-24

### Changed

- The npm source will ignore dependencies that are marked as both extraneous and missing (#347)
@jonabc jonabc mentioned this pull request Mar 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant