output: 'standalone' breaks Vercel deployments on Next 16.3 — ENOENT .next/next-server.js.nft.json in onBuildComplete

Important limitations

• This may be one public report, not widespread demand.
• Current independent report count: 1.
• This is currently a single independent report. It has not passed clustering or human review as a verified signal.
• No market size, willingness to pay, competition, or trend claims are inferred here.

What was reported

Who is affected

Frontend application developer

Job to be done

Deploy a service reliably

Workflow

Deploy to Vercel (vercel deploy)

Desired outcome

build succeeds (it does on next 16.2.11 with identical config, and locally on 16.3 with next build). Current: deterministic failure on Vercel. Reproduced on next@16.3.1-canary.1 (the reproduction template's default) and on 16.3.0; also hit in a production pnpm monorepo across 3 independent apps. Removing output: 'standalone' fixes every case immediately.

Severity

Not enough evidence yet.

Urgency

high

Evidence indicators

What would upgrade this

• Additional independent reports from distinct communities or authors.
• Human clustering into a review signal, then explicit publication approval.
• Counter-evidence review and durable original-source verification.

Original source

Open the original public report