fix(docs): recommend next "latest" instead of "*" for Vercel deployment - #3619
Merged
Merged
Conversation
Vercel's Next builder treats a "*" version range as a legacy Next.js project and force-installs next-server@7, which fails to resolve against React 19. "latest" is explicitly exempt from the legacy check. Verified with real deploys: "*" fails at npm install with ERESOLVE (peer react@^16 from next-server@7.0.2-canary.49), "latest" deploys and serves.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
dielduarte
approved these changes
Jul 2, 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.
The deployment docs tell users to add
"next": "*"todevDependenciesso Vercel's Next.js framework preset detects the project. But@vercel/nexttreats a*version range as a legacy Next.js project (isLegacyNextcheckssemver.maxSatisfyingagainst its legacy version list, which*matches) and force-installsnext-server@7, so the deploy fails duringnpm install:"latest"is explicitly exempt from the legacy check, and the rootnextversion is only used for framework detection — the preview app itself builds with the Next version pinned by@react-email/ui— solatestcannot drift out of sync with anything.Verified with real deployments of a stock
create-emailproject following the docs recipe:"next": "*"→ build fails atnpm installwith the ERESOLVE above"next": "latest"→ deploys green and the preview app servesRelated to the deployment issues reported in #3557.
Summary by cubic
Update Vercel deployment docs to use
next: "latest"instead of"*". This avoids@vercel/nextlegacy detection that installsnext-server@7and causes install failures, so deploys succeed.Written for commit 32d18ed. Summary will update on new commits.