Build error only on vercel

Build error only on vercel - Help - Vercel Community

(edited)

I get this error while building on vercel

> Build error occurred
Error: ENOENT: no such file or directory, open '/vercel/path0/.next/next-server.js.nft.json'
    at ignore-listed frames {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/vercel/path0/.next/next-server.js.nft.json'
}

meanwhile i can confirm this file exist while building on my local environment.

screenshot_2026-09-01T22:19:58.png

Vercel Staff

What happens if you run a local build with the CLI?

https://vercel.com/docs/cli/build

vercel.com

vercel build

Learn how to build a Vercel Project locally or in your own CI environment using the vercel build CLI command.

I am experiencing the same issue, using Next.js version 16.3.4.

Build error occurred Error: ENOENT: no such file or directory, open '/vercel/path0/.next/next-server.js.nft.json' at ignore-listed frames { errno: -2, code: 'ENOENT', syscall: 'open', path: '/vercel/path0/.next/next-server.js.nft.json' } Error: Command "npm run build" exited with 1

Running vercel build locally does seem to work.

Downgrading next.js to a lower version (I tried with version 16.2.6) also works.

Same pattern as L3keboy — if vercel build works locally but the cloud build misses next-server.js.nft.json, it is often a Next.js version / output-file-tracing mismatch on the Vercel builders. Pin the Next version that works (or match Node version in Project Settings to local), wipe .next from the repo if it was committed, and confirm the Install Command actually installs that same Next version on the build machine.

doing some more research the issue seems to be from output: standalone from the next.config

Yes, can confirm, removing output: standalone from the config fixes the problem!