---
title: Missing routes-manifest.json file or No Output Directory when using Turborepo or NX
description: How to solve the error `The file "/vercel/path0/apps/web/.next/routes-manifest.json" couldn't be found` or `No Output Directory` when using Turborepo or NX.
url: /kb/guide/missing-routes-manifest-or-output-turborepo-nx
canonical_url: "https://vercel.com/kb/guide/missing-routes-manifest-or-output-turborepo-nx"
published: 2025-11-03
last_updated: 2025-11-10
authors: Tilly Gee
related:
  - /docs/deployments/managing-deployments
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---
<!-- docsgraph:related -->
## Related pages

> **For AI agents:** Follow these links to understand how this page connects to the rest of the Vercel ecosystem. For the full cross-link map (inbound, outbound, prerequisites, and semantic neighbors), see the .graph.md link below.

- [Turborepo](https://vercel.com/docs/monorepos/turborepo?from=related) — Learn about Turborepo, a build system for monorepos that allows you to have faster incremental builds, content-aware has
- [Nx](https://vercel.com/docs/monorepos/nx?from=related) — Nx is an extensible build system with support for monorepos, integrations, and Remote Caching on Vercel. Learn how to de
- [Monorepos FAQ](https://vercel.com/docs/monorepos/monorepo-faq?from=related) — Learn the answer to common questions about deploying monorepos on Vercel.
- [Troubleshoot Build Errors](https://vercel.com/docs/deployments/troubleshoot-a-build?from=related) — Learn how to resolve common scenarios you may encounter during the Build step, including build errors that cancel a depl
- [Migrating from Nx](https://turborepo.dev/docs/guides/migrating-from-nx?from=related) — Step-by-step instructions for migrating your Nx monorepo to Turborepo.
- [Vercel](https://turborepo.dev/docs/guides/ci-vendors/vercel?from=related) — Deploy your Turborepo on Vercel with zero-config Remote Caching.
- [Debug Cache Issues](https://vercel.com/docs/caching/cdn-cache/debug-cache-issues?from=related) — Diagnose stale content and fix CDN cache, data cache, and build cache issues using the CLI.
- [Caching](https://turborepo.dev/docs/crafting-your-repository/caching?from=related) — Configure task caching to avoid repeating work, using fingerprinting for inputs and restoring outputs from cache.
- [How to debug 404 errors](https://vercel.com/kb/guide/how-to-debug-404-errors?from=related) — Learn the systematic steps to identify and resolve 404 issues.
- [Why is my deployed project giving a 404?](https://vercel.com/kb/guide/why-is-my-deployed-project-giving-404?from=related) — Vercel 404 errors often hit healthy builds when routing metadata does not match the request path. Learn the causes and h
- [Dependencies from package.json are missing after install](https://vercel.com/kb/guide/dependencies-from-package-json-missing-after-install?from=related) — Understand why dependencies may not being installed during a build and how to fix.

Full cross-link map for this page: [/kb/guide/missing-routes-manifest-or-output-turborepo-nx.graph.md](/kb/guide/missing-routes-manifest-or-output-turborepo-nx.graph.md)
<!-- /docsgraph:related -->


If you are experiencing the following error when deploying to Vercel using the Turborepo cache, it's likely the correct directories are not being cached between builds.

> _**The file "/vercel/path0/apps/web/.next/routes-manifest.json" couldn't be found**_

A similar issue may also be seen when using NX or may include the following error instead

> _**No Output Directory named "NAME"**_

Where "NAME" is the directory you have configured as the output.

A good way to determine if the problem lies with the cache would be to [redeploy your project](https://vercel.com/docs/deployments/managing-deployments#redeploy-a-project) without the cache and see if this resolves the issue. If it does then it's likely the output directories are not correctly configured in either your \`turbo.json\` or \`nx.json\`.

## Turborepo projects

For projects using Turborepo, take a look at their guide on [configuring cache outputs](https://turbo.build/repo/docs/core-concepts/caching/what-to-cache#configuring-cache-outputs). You can also check out their [example projects](https://github.com/vercel/turbo/tree/main/examples), these all include a \`turbo.json\` file so take a look at ones that use the same framework as your own project to see what has been included in \`outputs\`.

See the example \`turbo.json\` for a Next.js project

```json
{
  "$schema": "https://turborepo.com/schema.json",
  "pipeline": {
    "build": {
      "dependsOn": [
        "^build",
      ],
      "env": ["SOME_ENV_VAR", "API_KEY_VAR"],
      "outputs": [".next/**", "!.next/cache/**"] 
    },
    "web#build": {
      // override settings for the "build" task for the "web" app
      "dependsOn": [
        "^build",
      ],
      "env": ["SOME_OTHER_ENV_VAR"],
      "outputs": ["dist/**"]
    },
  },
  "globalEnv": [
    "GITHUB_TOKEN", // env var that will impact the hashes of all tasks,
  ],
  "globalDependencies": [
    "tsconfig.json" // file contents will impact the hashes of all tasks,
  ]
}
```

## NX projects

For NX projects, please take a look at their guide on [how caching works](https://nx.dev/concepts/how-caching-works#what-is-cached), including examples of correctly defining outputs either in your \`package.json\` or \`nx.json\` files.