How to resolve Error: The file "/vercel/path0/.next/routes-manifest.json" couldn't be found. #47517

lancejpollard · 2023-03-25T07:18:57Z

lancejpollard
Mar 25, 2023

Summary

I have been getting the following on Vercel builds/deployments continuously after somewhat halfway potentially resolving this other Vercel error:

(node:237) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
--
00:07:34.881 | (Use `node --trace-warnings ...` to show where the warning was created)
00:07:35.842 | info  - Linting and checking validity of types...
00:09:43.572 | Error: The file "/vercel/path0/.next/routes-manifest.json" couldn't be found. This is often caused by a misconfiguration in your project.
00:09:43.572 | Learn More: https://err.sh/vercel/vercel/now-next-routes-manifest
00:09:43.828 | NEXT_NO_ROUTES_MANIFEST: The file "/vercel/path0/.next/routes-manifest.json" couldn't be found. This is often caused by a misconfiguration in your project.

When I visit https://err.sh/vercel/vercel/now-next-routes-manifest, it talks about making sure your project settings are the default in Next.js on Vercel, which mine are (I double and triple checked).

Locally, I am able to run npm run lint with no errors, and npm run build works fine. I can develop my app fine as well with npm run dev.

I was facing that other hanging error before, but after removing most of the calls to loading JSON modules in the getServerSideProps, now I am getting this above error... Any ideas how I can fix this or what else might be happening?

Thank you.

P.S. Why am I not getting the same build response locally on my MacOS M2? Do I need to resort to simulating this somehow locally as a linux machine? If so, how can I do that do you think?

lancejpollard · 2023-03-25T07:26:08Z

lancejpollard
Mar 25, 2023
Author

One thing that seems weird, it says this in Vercel builds:

Detected `package-lock.json` generated by npm 7 ...

But when I do npm -v locally, I get 8.19.3. What should I do?

1 reply

lancejpollard Mar 25, 2023
Author

Tried switching to yarn, but same error:

Running build in Cleveland, USA (East) – cle1
--
00:34:00.730 | Cloning github.com/... (Branch: main, Commit: c92189b)
00:34:08.745 | Cloning completed: 8.015s
00:34:10.009 | Skipping build cache since Package Manager changed from "npm" to "yarn"
00:34:11.443 | Running "vercel build"
00:34:12.006 | Vercel CLI 28.18.1
00:34:12.460 | Installing dependencies...
00:34:12.837 | yarn install v1.22.17
00:34:12.933 | [1/4] Resolving packages...
00:34:13.402 | [2/4] Fetching packages...
00:34:49.437 | [3/4] Linking dependencies...
00:34:49.439 | warning " > @mdx-js/[email protected]" has unmet peer dependency "webpack@>=4".
00:34:49.441 | warning " > [email protected]" has unmet peer dependency "webpack@^4.0.0 \|\| ^5.0.0".
00:34:49.442 | warning " > [email protected]" has unmet peer dependency "react-is@>= 16.8.0".
00:35:02.165 | [4/4] Building fresh packages...
00:35:10.485 | Done in 57.65s.
00:35:10.519 | Detected Next.js version: 13.2.4
00:35:10.522 | Running "yarn run build"
00:35:10.740 | yarn run v1.22.17
00:35:10.785 | $ next build
00:35:11.431 | (node:410) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
00:35:11.431 | (Use `node --trace-warnings ...` to show where the warning was created)
00:35:12.216 | Attention: Next.js now collects completely anonymous telemetry regarding usage.
00:35:12.217 | This information is used to shape Next.js' roadmap and prioritize features.
00:35:12.217 | You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
00:35:12.217 | https://nextjs.org/telemetry
00:35:12.217 |  
00:35:12.416 | info  - Linting and checking validity of types...

Then:

Error: The file "/vercel/path1/.next/routes-manifest.json" couldn't be found. This is often caused by a misconfiguration in your project.
--
00:36:43.359 | Learn More: https://err.sh/vercel/vercel/now-next-routes-manifest
00:36:43.616 | NEXT_NO_ROUTES_MANIFEST: The file "/vercel/path1/.next/routes-manifest.json" couldn't be found. This is often caused by a misconfiguration in your project.

adelindanaila · 2023-04-01T09:20:11Z

adelindanaila
Apr 1, 2023

Same issue here, turborepo environment, the error seems to appear only when the preview -> production migration is happening.
After redeploying without build cache, everything is back to normal.

2 replies

lancejpollard Apr 12, 2023
Author

Mine seemed to have resolved with me just removing all the pages folder, and progressively adding them back, something just caused it to go away and I'm not sure what it was :/

anthonyshew Mar 21, 2024
Maintainer

I'm a little late but for anyone that ends up here after searching:

If you're seeing cache hits with turbo and things aren't being found in your build, you likely have misconfigured your outputs array. If you don't have an outputs array, Turborepo is unable to cache your build outputs, so a cache hit would result in restoring nothing from the cache.

DJanocha · 2023-04-22T11:16:41Z

DJanocha
Apr 22, 2023

In my case I got that error when trying to deploy a next.js project (called 'nextjs') inside of monorepo but didn't change the root directory to 'apps/nextjs'. So my problem was not about the commands overriding (build/install or whatever).

1 reply

giorgiabosello Jun 15, 2023

Thank you! Same!

AliWayne101 · 2023-05-06T14:56:59Z

AliWayne101
May 6, 2023

In my case i just removed distDir: 'build' from next.config.js

12 replies

KhizerWHussain May 31, 2024

Your Amazing, it works
May Allah bless you.

AtharvaKamble Jun 5, 2024

thank you so much! worked for me

Ali3905 Jul 31, 2024

In my case i just removed distDir: 'build' from next.config.js

work for me

waloZarate Sep 28, 2024

Thank you, it works for me too

rogerwillis Oct 9, 2024

Sweet! That's what did it for me as well!

Kinfe123 · 2023-06-05T07:31:21Z

Kinfe123
Jun 5, 2023

Hello there , mine is not working... i have done every step that you have suggested but still not working , the web is built using pnpm turbo nextjs

0 replies

kkcy · 2023-06-09T04:30:55Z

kkcy
Jun 9, 2023

I have the same issue, nextjs project with yarn. But it can be solve by clicking redeploy every time. Which is quite a hassle

0 replies

n2-freevas · 2023-06-16T06:13:30Z

n2-freevas
Jun 16, 2023

If we specify distDir in next.config.js,
You shoud input same name in Vercel > Build & Deployment Setting > Next.js > Output Directory.
(I tend to forget too.)

3 replies

jokereven Jul 30, 2023

that is my config, thanks.

basedfund Nov 24, 2023

This helped, thanks!

Shubham-Lal Dec 22, 2023

Thanks @n2-freevas, it fixed my deployment error.

thomasdavis · 2023-06-22T13:03:32Z

thomasdavis
Jun 22, 2023

I am in a turbo setup too, and mine has started triggering this error.

I checkout the last commit to work, made a new branch, made a change to the root README.md and pushed the branch.

It still triggers this error, I cannot figure out why my deployment is borked. I think it is something to do with Vercel.

Edit: I got mine working after 100 or so builds of doing stuff, not sure if this fixed it, but I tested changing this to and back, and it only succeeds when I use double quotes in my next.config.js

Good luck everyone else lol

1 reply

rlancejohnson Nov 29, 2023

This worked for us, thanks!

jpvalery · 2023-06-22T13:53:37Z

jpvalery
Jun 22, 2023

I had this error on a new folder/project in a turborepo setup and I found out that somehow Vercel was overriding the build command with something wrong (like cd to the root folder and then building in the wrong subfolder (which was the first folder in that projects folder)).

I disabled the override and it worked immediately

Hope this helps!

2 replies

nandorojo Aug 19, 2023

Thank you! Removing the override script where I called Turbo myself I think fixed it.

cred33 Oct 1, 2023

this worked beautifully! thank you

MiguelGGMM · 2023-07-11T22:02:03Z

MiguelGGMM
Jul 11, 2023

I removed output: 'export' from next.config.js and finally worked! for some reason build files were generated in .next folder instead of build for some reason, even when I had set distDir: build

0 replies

alexboii · 2023-08-01T19:15:07Z

alexboii
Aug 1, 2023

same issue here :/ no answer from vercel support of course. this is severely impacting our engineering team's productivity

0 replies

polooner · 2023-10-13T18:36:24Z

polooner
Oct 13, 2023

I encountered the same issue, I am using a monorepo structure with Turborepo. What worked for me is overriding my deployment/build commands on Vercel to these:
I have a basic workspaces setup:

apps/**
packages/**

4 replies

polooner Oct 13, 2023

And pnpm as shown.

joshy36 Oct 13, 2023

Super helpful, thanks. FYI, all i needed to do was change my output directory. Im using npm.

eyaleizenberg Apr 11, 2024

Worked for me as well (npm)

ace3 Apr 15, 2024

thats it's helped me also.

ludwighogstrom · 2023-10-27T14:24:18Z

ludwighogstrom
Oct 27, 2023

I had the same problem. It looks like it went away when I made sure all process.env variables used in the project were listed in the turbo file. See https://turbo.build/repo/docs/core-concepts/caching/environment-variable-inputs

The ESLint plugin eslint-config-turbo helped figure out which ones (https://turbo.build/blog/turbo-1-4-0#eslint-config-turbo).

0 replies

rlancejohnson · 2023-12-01T21:31:18Z

rlancejohnson
Dec 1, 2023

Have any of these changes actually fixed the problem for good? It seems like the issue will be resolved for us for a week or two and then show up again.

1 reply

ludwighogstrom Dec 2, 2023

My problem hasn't come back. See above about listing envs in turbo file #47517 (comment)

If the problem comes and goes it could have something to do with caching of the build? And that not having all used envs in turbo file makes the cache invalidation problematic.

Just guessing here though...

Barbeariafacil · 2024-01-17T21:31:04Z

Barbeariafacil
Jan 17, 2024

I resolved it by disabling the folder and path modules.

0 replies

kkcoms · 2024-02-15T12:16:29Z

kkcoms
Feb 15, 2024

Sometimes it helps

if you add /.next

/** @type {import('next').NextConfig} */
const nextConfig = {
  images: {
    domains: [
      "files.edgestore.dev"
    ]
  }
}

module.exports = nextConfig

0 replies

nateshirley · 2024-10-03T16:20:30Z

nateshirley
Oct 3, 2024

I ran into "vercel/path0: file not found" errors in a monorepo and fixed it by turning off the build cache. Set env var VERCEL_FORCE_NO_BUILD_CACHE=1 in project settings

0 replies

How to resolve Error: The file "/vercel/path0/.next/routes-manifest.json" couldn't be found. #47517

Summary

Replies: 17 comments · 27 replies

lancejpollard Mar 25, 2023 Author

lancejpollard Mar 25, 2023 Author

lancejpollard Apr 12, 2023 Author

anthonyshew Mar 21, 2024 Maintainer

Replies: 17 comments 27 replies

lancejpollard
Mar 25, 2023
Author

lancejpollard Mar 25, 2023
Author

lancejpollard Apr 12, 2023
Author

anthonyshew Mar 21, 2024
Maintainer