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.
pnpm v7.0.0 until 7.13.5 uses
--strict-peer-dependencies=true
which causes a failure when not allpeerDependencies
are installed. By setting the flag explicitly, this will no longer be a problem for new users.fix: #1806
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When a user uses pnpm 7.0.0 to 7.13.5 the install portion of
nest new
fails because of thestrict-peer-dependencies
option being set inherently totrue
, as we do not add every peer dependency to thepackage.json
Issue Number: #1806
What is the new behavior?
nest new
will no longer fail forpnpm
v7.0.0 to 7.13.5. Later versions it should be set tofalse
by default anywaysDoes this PR introduce a breaking change?
Other information