Repository navigation
chore: declare pnpm via devEngines.packageManager - #808
Merged
Merged
Conversation
✅ Deploy Preview for gitify ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
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
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.




Summary
Moves the pnpm pin from the legacy top-level
packageManagerfield intodevEngines.packageManager:"packageManager": "pnpm@12.14.0""devEngines": { ..., "packageManager": { "name": "pnpm", "version": "12.14.0", "onFail": "download" } }Same exact version, so there is no change to the resolved manager. pnpm 12 records it under
packageManagerDependenciesand can self-provision; Corepack ≥0.36 and bothpnpm/action-setupandpnpm/setupread the field.Notes:
corepack use pnpm@…would re-add the top-level field, so usecorepack installor editdevEnginesinstead.devEnginespath is the forward-looking one.Verification
package.jsonparses; no top-levelpackageManagerremainspnpm install --lockfile-onlyresolves the same pnpm version