3 people reported

All time, since Sep 1, including 1 thumbs-up on GitHub.

Build missing traced files, ENOENT

“Error: ENOENT: no such file or directory, open '/vercel/path0/.next/next-server.js.nft.json'”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/next-js/issues/4230/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Build output missing traced files, failing Vercel builds with ENOENT. Turbopack's nft.json trace lists a pnpm hoisted-store alias with no target files, or next-server.js.nft.json is missing on Vercel.

Is this your bug?

File my report
Where
output file tracing
Error text
Error: ENOENT: no such file or directory, open '/vercel/path0/.next/next-server.js.nft.json'
Versions
16.4.0-canary.32
Platforms
Linux
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. Turbopack traces a pnpm hoisted-store alias without its target files, producing a dangling symlink that fails Vercel deploys with ENOENTOn GitHub#98791
  2. Build error only on vercelOn the forum#48711

Do you work on Next.js?

Claim its RAP Sheet to see what your users report and answer them in one place.