feat(shim): block npm package-manager mismatch#1994
Closed
liangmiQwQ wants to merge 4 commits into
Closed
Conversation
✅ Deploy Preview for viteplus-preview canceled.
|
liangmiQwQ
changed the title
liangmiQwQ
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Close #1972
Top-level
npmshim calls now stop when the current project declares a different package manager inpackageManagerordevEngines.packageManager. The message mirrors Corepack's package-manager boundary and points users to the configured package manager.This keeps the existing recursion passthrough behavior for npm invoked from inside an already-dispatched shim process, and keeps matching npm declarations using the declared managed npm version.
This PR also adds a global snap fixture for a pnpm project invoking top-level npm.
🤖 Generated with Codex