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

fix: npm ls <pkg> with depth cli config #1862

Conversation

ruyadorno
Copy link
Contributor

Using the cli option --depth is currently not resulting in the expected
behavior of filtering depth level when running npm ls - that's due
the special behavior of printing all results when using a filter arg.

This commit fixes it by adding support to limiting depth if a config
value is set by the user.

Fixes #1861

@ruyadorno ruyadorno requested a review from a team as a code owner September 25, 2020 15:30
@ruyadorno ruyadorno added the Release 7.x work is associated with a specific npm 7 release label Sep 25, 2020
@ruyadorno ruyadorno added this to the OSS - Sprint 16 milestone Sep 25, 2020
lib/ls.js Outdated Show resolved Hide resolved
Using the cli option --depth is currently not resulting in the expected
behavior of filtering depth level when running npm ls <pkg> - that's due
the special behavior of printing all results when using a filter arg.

This commit fixes it by adding support to limiting depth if a config
value is set by the user.

Fixes npm#1861
nlf pushed a commit that referenced this pull request Sep 29, 2020
Using the cli option --depth is currently not resulting in the expected
behavior of filtering depth level when running npm ls <pkg> - that's due
the special behavior of printing all results when using a filter arg.

This commit fixes it by adding support to limiting depth if a config
value is set by the user.

Fixes #1861

PR-URL: #1862
Credit: @ruyadorno
Close: #1862
Reviewed-by: @nlf
nlf pushed a commit that referenced this pull request Sep 29, 2020
Using the cli option --depth is currently not resulting in the expected
behavior of filtering depth level when running npm ls <pkg> - that's due
the special behavior of printing all results when using a filter arg.

This commit fixes it by adding support to limiting depth if a config
value is set by the user.

Fixes #1861

PR-URL: #1862
Credit: @ruyadorno
Close: #1862
Reviewed-by: @nlf
@ruyadorno ruyadorno closed this Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Release 7.x work is associated with a specific npm 7 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants