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

Figure out the story for onlySpecified in npm@3 #20

Open
mgol opened this issue Sep 23, 2015 · 2 comments
Open

Figure out the story for onlySpecified in npm@3 #20

mgol opened this issue Sep 23, 2015 · 2 comments

Comments

@mgol
Copy link
Owner

mgol commented Sep 23, 2015

npm 3 dedupes sub-dependencies by default which means node_modules contains many dependencies of dependencies directly, making the onlySpecified option to not work as it should.

We need to figure out what to do in such a case. Currently README contains a warning against using this option with npm@3. npm ls prints such info but it's very slow, way more than in npm@2 and one of the main goals of this module was to make this whole checking as fast as possible.

This option is still useful for bower so I don't think we want to depreciate it.

@treythomas123
Copy link

This would be nice to have. Basically a dry run of npm prune to see if there's any unnecessary packages hanging around.

@simlu
Copy link

simlu commented Dec 7, 2017

I'd also very much love to have this option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants