---
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
---

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.

## More Next.js guides

- [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.
- [Migrate a Next.js app from Webflow Cloud to Vercel](/kb/guide/migrate-a-next-js-app-from-webflow-cloud-to-vercel): Move your Next.js app from Webflow Cloud to Vercel: remove the OpenNext Cloudflare adapter, drop the base path, map storage bindings to Vercel Blob, Redis, and Postgres, and deploy with Git or the vercel CLI.
- [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.