change nextjs packageManager version#1274
Merged
Merged
Conversation
technophile-04
added a commit
to scaffold-eth/create-eth
that referenced
this pull request
Apr 21, 2026
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
2 participants
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.
Description
Forge to update the
packageMangerinpackages/nextjs/package.jsonat #1211.I initially thought of just removing this field from the
packages/nextjs/package.jsonbecause any which ways while dong theyarn installthe corepack looks only at the root package.json version but we actaully reqruire this because ofyarn vercelbecause there we are just uploading thenextjspackage to vercel so it doesn't have any context about the yarn version.