[bugfix]: specify depth in npm ls
to avoid errors from uninstalled peerDeps
#1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In
npm v8
, thels
command will default to--depth=0
, but to be safe, we'll include it for now.Context:
While attempting to run the CLI in a project that had some dependencies with missing
peerDeps
, it crashed because ofnpm
errors relating to them. Usingdepth=0
explicitly will avoid this because dependencies (prod, dev, and peer) that are specified inpackage.json
will always be included afternpm install
.