# Using Monorepos

Monorepos allow you to manage multiple projects in a single directory. They are a great way to organize your projects and make them easier to work with.

## Deploy a template monorepo

Get started with monorepos on Vercel in a few minutes by using one of our monorepo quickstart templates.

## Add a monorepo through the Vercel Dashboard

1. Go to the [Vercel Dashboard](https://vercel.com/dashboard) and ensure your team is selected from the [scope selector](/docs/dashboard-features#scope-selector).
2. Select the **Add New…** button, and then choose **Project** from the list. You'll create a new [project](/docs/projects/overview) for each directory in your monorepo that you wish to import.
3. From the **Import Git Repository** section, select the **Import** button next to the repository you want to import.
4. Before you deploy, you'll need to specify the directory within your monorepo that you want to deploy. Click the **Edit** button next to the [Root Directory setting](/docs/deployments/configure-a-build#root-directory) to select the directory, or project, you want to deploy. This will configure the root directory of each project to its relevant directory in the repository:

5) Configure any necessary settings and click the **Deploy** button to deploy that project.
6) Repeat steps 2-5 to [import each directory](/docs/git#deploying-a-git-repository) from your monorepo that you want to deploy.

Once you've created a separate project for each of the directories within your Git repository, every commit will issue a deployment for all connected projects and display the resulting URLs on your pull requests and commits:

The number of Vercel Projects connected with the same Git repository is [limited depending on your plan](/docs/limits#general-limits).

## Add a monorepo through Vercel CLI

> **💡 Note:** You should use [Vercel CLI 20.1.0](/docs/cli#updating-vercel-cli) or newer.

1. Ensure you're in the root directory of your monorepo. Vercel CLI should not be invoked from the subdirectory.
2. Run `vercel link` to link multiple Vercel projects at once. To learn more, see the [CLI documentation](/docs/cli/link#repo-alpha):
   ```bash filename="Terminal"
   vercel link --repo
   ```
3. Once linked, subsequent commands such as `vercel dev` will use the selected Vercel Project. To switch to a different Project in the same monorepo, run `vercel link` again and select the new Project.

Alternatively, you can use  to create multiple copies of your monorepo in different directories and link each one to a different Vercel Project.

> **💡 Note:** See this [example](https://github.com/vercel-support/yarn-ws-monorepo) of a
> monorepo with Yarn Workspaces.

## When does a monorepo build occur?

By default, pushing a commit to your monorepo will create a deployment for each of the connected Vercel projects. However, you can choose to:

- [Skip unaffected projects](#skipping-unaffected-projects) by only building projects whose files have changed.
- [Ignore the build step](#ignoring-the-build-step) for projects whose files have not changed.

### Skipping unaffected projects

A project in a monorepo is considered to be changed if any of the following conditions are true:

1. The project source code has changed
2. Any of the project's internal dependencies have changed.
3. A change to a package manager lockfile has occurred, that *only* impacts the dependencies of the project.

Vercel automatically skips builds for projects in a monorepo that are unchanged by the commit.

This setting does **not** occupy [concurrent build slots](/docs/deployments/concurrent-builds), unlike the [Ignored Build Step](/docs/project-configuration/project-settings#ignored-build-step) feature, reducing build queue times.

#### Requirements

- This feature is only available for projects connected to GitHub repositories.
- The monorepo must be using npm, yarn, or pnpm workspaces, following JavaScript ecosystem conventions. Packages in the workspace must be included in the workspace definition (`workspaces` key in `package.json` for npm and yarn or `pnpm-workspace.yaml` for pnpm).
  - Changes that are not a part of the workspace definition will be considered global changes and deploy all applications in the repository.
  - We automatically detect your package manager using the lockfile at the repository root. You can also explicitly set a package manager with the `packageManager` field in root `package.json` file.
- All packages within the workspace must have a **unique** `name` field in their `package.json` file.
- Dependencies between packages in the monorepo must be explicitly stated in each package's `package.json` file. This is necessary to determine the dependency graph between packages.
  - For example, an end-to-end tests package (`package-e2e`) tests must depend on the package it tests (`package-core`) in the `package.json` of `package-e2e`.

#### Disable the skipping unaffected projects feature

To disable this behavior, [visit the project's Root Directory settings](https://vercel.com/d?to=%2F%5Bteam%5D%2F%5Bproject%5D%2Fsettings%2Fbuild-and-deployment%23root-directory\&title=Disable+unaffected+project+skipping).

1. From the [Dashboard](https://vercel.com/dashboard), select the project you want to configure and navigate to the **Settings** tab.
2. Go to the Build and Deployment page of the project's Settings.
3. Scroll down to **Root Directory**
4. Toggle the **Skip deployment** switch to **Disabled**.
5. Click **Save** to apply the changes.

### Ignoring the build step

If you want to cancel the Build Step for projects if their files didn't change, you can do so with the [Ignored Build Step](/docs/project-configuration/project-settings#ignored-build-step) project setting. Canceled builds initiated using the ignore build step do count towards your deployment and concurrent build limits and so [skipping unaffected projects](#skipping-unaffected-projects) may be a better option for monorepos with many projects.

If you have created a script to ignore the build step, you can skip the [the
script](/kb/guide/how-do-i-use-the-ignored-build-step-field-on-vercel) when
redeploying or promoting your app to production. This can be done through the
dashboard when you click on the **Redeploy** button, and unchecking the **Use
project's Ignore Build Step** checkbox.

## How to link projects together in a monorepo

When working in a monorepo with multiple applications—such as a frontend and a backend—it can be challenging to manage the connection strings between environments to ensure a seamless experience.
Traditionally, referencing one project from another requires manually setting URLs or environment variables for each deployment, in *every* environment.

With Related Projects, this process is streamlined, enabling teams to:

- Verify changes in pre-production environments without manually updating URLs or environment variables.
- Eliminate misconfigurations when referencing internal services across multiple deployments, and environments.

For example, if your monorepo contains:

1. A frontend project that fetches data from an API
2. A backend API project that serves the data

Related Projects can ensure that each preview deployment of the frontend automatically references the corresponding preview deployment of the backend, avoiding the need for hardcoded environment variables when testing
changes that span both projects.

### Requirements

- A maximum of 3 projects can be linked together
- Only supports projects within the same repository
- CLI deployments are not supported

### Getting started

- ### Define Related Projects
  Specify the projects your app needs to reference in a `vercel.json` configuration file at the root of the app.
  While every app in your monorepo can list related projects in their own `vercel.json`, you can only specify up to three related projects per app.
  ```json filename="apps/frontend/vercel.json"
  {
    "relatedProjects": ["prj_123"]
  }
  ```
  This will make the preview, and production hosts of `prj_123` available as an environment variable in the deployment of the `frontend` project.
  > **💡 Note:** You can [find your project
  > ID](https://vercel.com/d?to=%2F%5Bteam%5D%2F%5Bproject%5D%2Fsettings%23project-id\&title=Find+your+Vercel+project+ID)
  > in the project **Settings** page in the Vercel dashboard.

- ### Retrieve Related Project Information
  The next deployment will have the `VERCEL_RELATED_PROJECTS` environment variable set containing the urls of the related projects for use.
  > **💡 Note:** View the data provided for each project in the
  > [`@vercel/related-projects`](https://github.com/vercel/vercel/blob/main/packages/related-projects/src/types.ts#L9-L58)
  > package.
  For easy access to this information, you can use the [`@vercel/related-projects`](https://github.com/vercel/vercel/tree/main/packages/related-projects) npm package:
  ```bash filename="Terminal" package-manager="npm"
  npm i @vercel/related-projects
  ```
  ```bash filename="Terminal" package-manager="bun"
  bun add @vercel/related-projects
  ```
  ```bash filename="Terminal" package-manager="yarn"
  yarn add @vercel/related-projects
  ```
  ```bash filename="Terminal" package-manager="pnpm"
  pnpm add @vercel/related-projects
  ```
  1. Easily reference hosts of related projects
  ```ts
  import { withRelatedProject } from '@vercel/related-projects';

  const apiHost = withRelatedProject({
    projectName: 'my-api-project',
    /**
     * Specify a default host that will be used for my-api-project if the related project
     * data cannot be parsed or is missing.
     */
    defaultHost: process.env.API_HOST,
  });
  ```
  2. Retrieve just the related project data:
  ```ts filename="index.ts"
  import {
    relatedProjects,
    type VercelRelatedProject,
  } from '@vercel/related-projects';

  // fully typed project data
  const projects: VercelRelatedProject[] = relatedProjects();
  ```


--------------------------------------------------------------------------------
title: "Remote Caching"
description: "Vercel Remote Cache allows you to share build outputs and artifacts across distributed teams."
last_updated: "2026-02-03T02:58:46.305Z"
source: "https://vercel.com/docs/monorepos/remote-caching"
--------------------------------------------------------------------------------