Next.js build succeeds but fails with duplicated path /vercel/path0/vercel/path0

Help
1

Current behavior
My project builds successfully with Next.js 16 (✓ Compiled successfully, all pages generated), but the post-build step fails with:Current behavior
My project builds successfully with Next.js 16 (✓ Compiled successfully, all pages generated), but the post-build step fails with:

The build output exists at /vercel/path0/.next, but Vercel’s packager looks one directory deeper.
Expected behavior
After a successful build, Vercel should locate .next/routes-manifest.json and upload the build output without error.
Steps to reproduce

  1. Push to the main branch of SPLAT-Admin/splat-landing-lite.
  2. Vercel build completes successfully (Next.js 16.0.7).
  3. Post-build phase fails with the above ENOENT error.
    Project information
  • Framework: Next.js 16.0.7
  • Package manager: pnpm 10.x
  • Build command: pnpm run build
  • Install command: pnpm install --frozen-lockfile
  • Output directory: .next
  • Root Directory (Dashboard): blank
  • .vercel/project.json: no "path" entry
  • Account plan: Hobby
  • Region: PDX1 (Portland, USA – West)
    Additional details
    Everything in the build succeeds; this appears to be internal metadata caching for buildOutputPath or rootDirectory from an older import of the project.
    Please reset the internal path configuration so the bundler looks in /vercel/path0/.next instead of /vercel/path0/vercel/path0/.next.
    Thank you!

#help #builds #vercel-bug

4

HI @splat-admin, welcome to the Vercel Community!

I’m sorry that you’re facing this issue.

Have you tried running vercel build from the local project? Can you share the output from there?

Also, I’d recommend using the default framework presets from the Project settings on the Vercel dashboard and revert to default on next.config and vercel.json as well.

Can you give it a shot and let me know what is the outcome?

5

Hi Anshuman,

Thanks for checking in.

Yes — I’ve already tested the build locally using pnpm run build and vercel build.

Both succeed completely and produce a valid .next/routes-manifest.json in the expected /splat-landing-clean/.next folder.

The issue only happens after the build completes on Vercel’s servers:

Error: ENOENT: no such file or directory, lstat ‘/vercel/path0/vercel/path0/.next/routes-manifest.json’

The extra /vercel/path0 in that path indicates an internal cached root or buildOutputPath.

I’ve already reverted to the default framework preset (Next.js) and confirmed that:

  • Root Directory is blank

  • next.config.js and vercel.json are default

  • .vercel/project.json has no “path” entry

Could you please escalate this so the internal build path metadata for this project can be reset?

Other users with the same duplicated /vercel/path0/vercel/path0 error had it resolved only after a metadata reset on Vercel’s side.

Thanks again for your help!

6

Thanks for confirming this.

Can you delete and recreate this project? I think this would be a faster fix. Also, can you share the links to the other posts you are talking about?

7

Hey @splat-admin, just checking in on your issue with the duplicated path in the Vercel build. Have you had a chance to try deleting and recreating the project? Let me know if you still need assistance or found a solution.