Vercel deploys invalid version of turborepo app

Help
4

It’s great to see you here, @mezotv! Thank you for posting and welcome to the Community :grinning_face_with_smiling_eyes:

Have you had a chance to check out our debugging 404 errors post? It might be helpful while you’re digging into this.

Looking at your issue, it seems like Vercel is rebuilding both apps in your Turborepo even when only non-app files are changed and as a result, the web app ends up deploying in an invalid state.

This usually happens because Vercel’s default behavior is to rebuild all linked projects whenever any file changes, even if those changes don’t affect the apps themselves.

A few things you can try:

First, you can configure an ignored build step in your web app’s vercel.json so that Vercel only rebuilds when certain files change:

{
  "ignoreCommand": "git diff HEAD^ HEAD --quiet ./src ./public ./package.json ./astro.config.mjs"
}

Next, since you’re already using Turborepo, you can take advantage of Turbo’s built-in filtering. In your Vercel project settings, set your build command to:

turbo build --filter=web...

This ensures that only the web app (or its dependencies) gets built when relevant files are updated.

You can also double-check your turbo.json configuration to make sure dependency mappings are set up correctly, so Turbo knows when each app actually needs to rebuild.

Let us know how you get on!

1 Like