fix(proxy): override Vercel build command so it doesn't run turbo#13448
Merged
Conversation
The proxy is intentionally outside the pnpm workspace and has no build step (it ships as Vercel Functions compiled from api/). Vercel was auto-detecting Turbo and defaulting the build command to `turbo run build`, which fails with "Could not find task build in project" because the isolated proxy package has no turbo.json or build task. Add a vercel.json with an explicit no-op buildCommand so Vercel skips turbo; the api/ functions are still detected and deployed.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
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.
☕️ Reasoning
The
proxyVercel deployment onmainfails during build:(from
npx vercel inspect dpl_R6Qy53byKXgidYV2zVKzg2KJ7QGL --logs)Root cause:
apps/proxyis intentionally outside the pnpm workspace (pnpm-workspace.yamlcoverspackages/*,apps/dev/*,docsonly) and is installed withpnpm install --ignore-workspace. It has no build step — it ships as Vercel Functions compiled fromapi/(api/[auth].ts,api/callback/[auth].ts). Vercel auto-detects Turbo and sets the default build command toturbo run build, but the isolated proxy package has noturbo.jsonand nobuildtask, so the command errors before the functions are ever built.Fix: add
apps/proxy/vercel.jsonwith an explicit no-opbuildCommand, so Vercel skips the turbo default. Theapi/functions are still detected and deployed as before.🧢 Checklist