You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
; copy and paste output from `npm config ls` here; node bin location = /Users/sethtomy/.nvm/versions/node/v22.11.0/bin/node; node version = v22.11.0; npm local prefix = /Users/sethtomy/Developer/open-source/minimal-reproduction-repos/npm-ls-issue; npm version = 10.9.0; cwd = /Users/sethtomy/Developer/open-source/minimal-reproduction-repos/npm-ls-issue; HOME = /Users/sethtomy; Run `npm config ls -l` to show all defaults.
The text was updated successfully, but these errors were encountered:
What about npm explain cross-spawn? That may be more helpful.
It's definitely an alternative option. Perhaps this is just a documentation issue? My thought process is that running "npm install" installs both dev and production dependencies so I'd expect "npm ls" to be consistent.
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
When running
npm ls INSERT_DEPENDENCY
I am only getting back those installation underneath the dev dependencies.If I run
npm ls --prod INSERT_DEPENDENCY
then I can see the missing dependency.Expected Behavior
I would expect that
npm ls INSERT_DEPENDENCY
by default would list both dev and production dependencies.Steps To Reproduce
minimal repro
Environment
The text was updated successfully, but these errors were encountered: