feat(pnp)!: default pnpFallbackMode to none
#5597
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
We'll certainly have to do that, but I'm a bit concerned about landing this right now, "so close" from the formal release. We have good confidence that the 4.x won't break significant stuff, but this change could redistribute the cards. What do you think about deferring it to the next major? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's the problem this PR addresses?
By default PnP allows dependencies to access the dependencies of the top-level package through the
pnpFallbackModeoption.This can cause some projects to stop working when moved to a workspace which can be seen as unexpected by users.
How did you fix it?
Default
pnpFallbackModetonone.Checklist