Bug: Not found routes-manifest.json at deploying by Vercel. v10.0.8

[aiji42]

What version of Next.js are you using?

10.0.8

What version of Node.js are you using?

14.16.0

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

Vercel

Describe the Bug

When I deploy vercel, I get an error after the build step. I have confirmed that no error occurs in v10.0.7.

23:32:15.953  	Traced Next.js server files in: 11311.251ms
23:32:15.958  	[Error: ENOENT: no such file or directory, lstat '/.next/routes-manifest.json'] {
23:32:15.958  	  errno: -2,
23:32:15.958  	  code: 'ENOENT',
23:32:15.958  	  syscall: 'lstat',
23:32:15.958  	  path: '/.next/routes-manifest.json'
23:32:15.959  	}
23:32:18.607  	Done with "package.json"

Expected Behavior

Expect the deployment to be successful.

To Reproduce

1. install NextJS v10.0.8
2. create ssr page application
3. deploy by Vercel

[ijjk]

Hi, I'm not able to reproduce this on a minimal Next.js app with a SSR page as described, please provide a minimal reproduction where you are seeing this occur and we can investigate further!

[underfisk]

@ijjk i do have the same issue, https://github.com/underfisk/vercel-issue-app and just follow nx override paths to specify the dist directory and the build command, it happened all of the sudden and this is not good for us, we have a deployment delayed due to the fact this error occurred from nowhere

[aiji42]

I'm also having this problem with a Nx project.
@underfisk, thank you for the supplement.

[underfisk]

I'm using Nx too, not only the builds stopped working, env variables are no longer being passed, next/image is complaining of hostname when i clearly have AWS s3 domain in there, i'm just sure that something was updated on the framework/vercel that is causing this

[ijjk]

Thanks for the reproduction, note downgrading to v10.0.7 should unblock your deployment while this is investigated.

[underfisk]

@ijjk Were you able to check the issues with the routes? I did try with 10.0.7 but seems that i have the same issue, did you deploy in a vercel environment?

[ijjk]

@underfisk did the lockfile get updated correctly? I used your example app and after downgrading to v10.0.7 it deploys successfully. Example deployment here.

Note: we are actively investigating a fix for v10.0.8 and will update here once it is landed.

[underfisk]

@ijjk I did have the lockfile ignored (i use pnpm) and i added it back on git. The issue remains even though i rollback to v10.0.7 and the lstat persists but as i said, it just happens with Vercel deployment, i tried deploying to a custom S3 and it work fine using build + export command and the routes-manifest.json does exist in there, now i'm not sure what actually did change on the vercel infrastructure but it did stop working

[underfisk]

@ijjk I have tested latest canary even with the fix for this matter and the issue still persists (deploying to Vercel)

[ijjk]

@underfisk yes the fix is almost rolled out, will update here when it is

[underfisk]

@ijjk Okay thank you, this was something very important for us (my company) because since last weeks we have delayed builds, we tried rollbacking the versions but nothing, everything stopped

[ijjk]

@underfisk it sounds like you are having trouble rolling back the version due to ignoring your lockfile. The lockfile helps ensure the same versions of your packages are used across installations and should be committed to your repo.

[underfisk]

@ijjk Indeed, i tried using old lockfiles, tried ignoring on git so vercel could create one from scratch, tried using a newer but nothing, in combination i do use Nx so its hard to identify whether its vercel or nx related, it just happen all of the sudden even when we were using vercel 10.0.7 but Nx could have upgrade to this 10.0.8 version

[ijjk]

Hi, this should be resolved now on v10.0.8 or the new stable release v10.0.9 if you are still encountering problems with this please respond here so we can investigate further!

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.