Turborepo deployment to Vercel using vercel CLI

[iambryancs]

Summary

Have anyone tried deploying a turborepo consisting of two apps (nextjs, hono) to vercel using the cli? It's easy to deploy when using git repositories with built-in integration to Vercel but for other repositories, we have to use the cli.

Here's what I did so far:

1. Setup turborepo with 2 apps
2. Tried deploying the nextjs app first to Vercel using the cli but I'm stuck here

Here's my directory setup:

❯ tree -L 2                                                                                          ─╯
.
├── README.md
├── apps
│   ├── api
│   └── client
├── biome.json
├── node_modules
│   ├── @biomejs
│   ├── @eslint
│   ├── @eslint-community
│   ├── @next
│   ├── @repo
│   ├── ...
├── package.json
├── packages
│   ├── eslint-config
│   ├── typescript-config
│   └── ui
├── pnpm-lock.yaml
├── pnpm-workspace.yaml
├── turbo.json

Running vercel with --cwd=apps/client doesn't seem to take into account the root directory of the turborepo as I'm getting. Inspecting the source in Vercel dashboard only shows the contents of apps/client which is why the error shows.

❯ vercel --prod --cwd apps/client                                        ─╯
Vercel CLI 41.5.0
�  Inspect: https://vercel.com/freshclinics/client/7M2pKbgWniiR7bh3wn4tQWgveqxk [1s]
✅  Production: https://client-67j7nj34d-freshclinics.vercel.app [1s]
Error: No Next.js version could be detected in your project. Make sure `"next"` is installed in "dependencies" or "devDependencies"

I understand that a vercel project has to be created/present in each apps but that somehow causes the root turborepo to be ignored? If I create a vercel project in the root of the turborepo it works but only 1 app is deployed.

Additional information

No response

Example

No response

[jmotes]

I've been working through something similar.

I tried using cwd too but learned that causes more problems than it's worth.

What does seem to work well is using vercel pull to fetch the project settings from Vercel, and handling just project at a time within the repository root. Within the Vercel portal, I have the Root Directory set on the project (under the Build and Deployment tab) that vercel pull retrieves, so that negates the need to use cwd.

This article was helpful for me if you haven't seen it yet:

https://vercel.com/guides/how-can-i-use-github-actions-with-vercel