-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 ls only listing dev dependencies by default #7917
Comments
What about |
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. |
@sethtomy I tried the npm ls and all the dependencies and devDependencies are listed as expected. If you still think this is an issue, please provide more details to troubleshoot. |
@kchindam-infy thanks for looking! Did you use my minimal reproduction repo? I put a link in the issue. |
@kchindam-infy can you run the below and see the output? This is the issue I'm facing. npm ls cross-spawn
# ├─┬ @nestjs/[email protected]
# │ └─┬ [email protected]
# │ └─┬ [email protected]
# │ └── [email protected] deduped
# ├─┬ [email protected]
# │ └── [email protected]
# └─┬ [email protected]
# └─┬ @jest/[email protected]
# └─┬ [email protected]
# └─┬ [email protected]
# └── [email protected] deduped |
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: