Conversation
pnpm now treats the top-level packageManager field as legacy in favor of devEngines.packageManager, which supports version ranges and a per-field onFail, mirroring how this project already pins its Node.js version via devEngines.runtime. Closes #1212 Signed-off-by: Alfi Maulana <alfi.maulana.f@gmail.com>
threeal
added
enhancement
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.
pnpm now treats the top-level
packageManagerfield as legacy in favor ofdevEngines.packageManager, which supports version ranges and a per-fieldonFail— the same shape this project already uses to pin its Node.js version viadevEngines.runtime. This replaces the pnpm pin with adevEngines.packageManagerentry mirroring that existing block.Closes #1212