Integrating v0 with existing GitHub repositories and Vercel projects

Help
,
15

@mayven I think this may be the root of the problem or at least one of the problems:

This is a hard limitation of the v0 environment that I need to surface honestly.

**The v0 build pipeline requires the Next.js app root at the repository root (/).** The build system runs next dev / next build from /vercel/share/v0-project/ and expects next.config.mjs, package.json, tsconfig.json, and app/ to exist at that level. There is no way to configure it to target apps/web as the build root – there is no Turborepo workspace support, no custom rootDir override, and no way to change the working directory of the build command.

Concretely, if I move everything under apps/web/:

  • The dev server will fail because it won’t find next.config.mjs at root
  • package.json at root is what drives dependency installation – a nested one won’t be picked up
  • The preview/deploy pipeline has no mechanism to cd apps/web && next build

It feels like v0 really expects a pretty strict environment to work in - I would assume more flexibility given its’ trying to work in ‘other peoples repos’ - but again maybe I am missing some fundamental point here…