-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[BUG] npm dedupe is not running during npm install #1179
Comments
Deduping isn't always a safe operation; npm install shouldn't dedupe by default. If you want that, run |
@ljharb The reason I can't reproduce this at the moment is because If I start without ❯ npm i
added 136 packages from 120 contributors and audited 1222 packages in 1.482s
2 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
❯ npm ls solid-js
@lume/create@ /home/trusktr/src/npm+cli
└── (empty)
❯ npm i @lume/element
+ @lume/[email protected]
added 17 packages from 30 contributors and audited 1253 packages in 2.878s
2 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
❯ npm ls solid-js
@lume/create@ /home/trusktr/src/npm+cli
└─┬ @lume/[email protected]
├─┬ @lume/[email protected]
│ └── [email protected] deduped
└── [email protected] Note the That's always the case. Otherwise I'd have ran into many issues by now with libs exporting singletons (React, Solid, etc). |
If |
Anywho, |
What
I ran
npm install
in a project, then mynpm ls
output showed:Notice it does not say
deduped
anywhere.Then I had to manually run
npm dedupe
for things to be deduped:And now
deduped
appeared in thenpm ls
output.Steps to Reproduce
I am unable to reproduce at the moment, but what I described above is exactly what I observed.
If I encounter it again, I will come back.
Expected Behavior
npm install
should dedupe things.The text was updated successfully, but these errors were encountered: