Repository navigation
Fix the Vercel build and make the Vercel setup one-click - #2
Merged
Merged
Conversation
…ob auto-detected Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QktEqYfYA1H2gQRbvG88pU
…ation, fail fast without a remote database Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QktEqYfYA1H2gQRbvG88pU
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QktEqYfYA1H2gQRbvG88pU
This branch had an error being deployed
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.
Why
The first production deploy of the
vitrinaVercel project (commit52f9522) failed withENOENT .next/next-server.js.nft.json: Vercel's packaging trips overoutput: "standalone". The build log also showed the migration running against a local file database because no Turso variables were present.What changes
next.config.ts:output: "standalone"only when not building on Vercel (the Dockerfile still gets it).src/instrumentation.ts+src/instrumentation-node.ts: the boot migration lives in a Node-only module behind the runtime check, so the edge bundle no longer warns; it is skipped on Vercel wherevercel-buildmigrates at build time.scripts/migrate.mjs: on Vercel, afile:database is a configuration error — the build fails immediately with the exact fix instead of shipping a broken deployment.TURSO_DATABASE_URL/TURSO_AUTH_TOKENhonoured,vercel-buildscript, Blob storage detected fromBLOB_READ_WRITE_TOKENalone.Verified
VERCEL=1 pnpm buildsucceeds with no standalone output; plainpnpm buildstill produces it.VERCEL=1 node scripts/migrate.mjsexits 1 with the message when no remote database is configured.After merging
Set in the Vercel project (Settings → Environment Variables):
APP_SECRET,APP_URL,HF_API_BASE_URL,PLATFORM_API_KEY; add the Turso integration and a Blob store. Seedocs/DEPLOY.md.🤖 Generated with Claude Code
https://claude.ai/code/session_01QktEqYfYA1H2gQRbvG88pU
Generated by Claude Code