---
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: "https://vercel.com/kb/guide/missing-routes-manifest-or-output-turborepo-nx"
published: 2025-11-03
last_updated: 2026-09-28
authors: Tilly Gee
install_vercel_plugin: npx plugins add vercel/vercel-plugin
search_with_vercel_cli: npx vercel@latest kb search "<query>"
read_with_vercel_cli: "npx vercel@latest kb inspect missing-routes-manifest-or-output-turborepo-nx"
---

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.

## Related Documentation

- [Next.js](/docs/frameworks/full-stack/nextjs)

## More Next.js guides

- [Vercel vs Webflow Cloud](/kb/guide/vercel-vs-webflow-cloud): Compare Vercel and Webflow Cloud for deploying Next.js and Astro apps, including runtime, framework support, storage, pricing, and where your code runs.
- [Next.js on Vercel vs Webflow Cloud](/kb/guide/next-js-on-vercel-vs-webflow-cloud): Compare running Next.js on Vercel Functions with Fluid compute against Webflow Cloud on Cloudflare Workers. Learn how Next.js feature support, runtimes, storage, pricing, and developer experience differ so you can choose the right platform.
- [Build an AI Chat Agent with Weather API Tool Calling](/kb/guide/build-ai-agent-weather-api): Build an intelligent conversational agent that fetches real-time weather data using the AI SDK, tool calling, and a backend weather API powered by Express, FastAPI or Nitro

## Reference Architecture

Choose a stack and work through the decisions behind it, with curated documentation, guides, templates, and courses to help you build.

- [Agent stack](/kb/architecture/agents): Build and operate agents with models, tools, and durable workflows.
- [Web applications](/kb/architecture/web): Choose rendering, data, authentication, and caching approaches.
- [Backends](/kb/architecture/backends): Choose a runtime, connect services, and run background work.

[Browse all stacks](/kb/architecture)

## Build with prompts

Build an app, extend an agent, or improve your project with ready-to-use prompts for your coding agent.

[Browse the prompt library](/kb/prompts) · [Read the Markdown index](/kb/prompts.md)

## Search guides from your terminal

Search the Knowledge Base and read guides as Markdown with the Vercel CLI. No login required.

```bash
# Find guides by keyword
npx vercel@latest kb search "rewrites and redirects"
npx vercel@latest kb search "AI SDK streaming"

# Show the latest guides
npx vercel@latest kb

# Print a guide as Markdown, by slug or URL
npx vercel@latest kb inspect <guide>
```