16.3.0: `output: 'standalone'` + adapter crashes `next build` — #93684 stops emitting next-server.js.nft.json but copyTracedFiles still requires it

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

Any app with `output: 'standalone'` in its config (common for teams that also deploy via Docker) fails to deploy on 16.3.0, while 16.2.12 works (the 16.2 branch never received the #93684 gate).

Desired outcome

** either the root NFT files are still emitted when `output: 'standalone'` is set (standalone needs them regardless of the adapter), or standalone+adapter is rejected early with a clear error — the code already anticipates this: `build/index.ts` carries the comment *"in the future output: standalone might not be allowed if an adapter with onBuildComplete is configured"*. A silent ENOENT from deep inside the finalize step is the worst of both.

Severity

Not enough evidence yet.

Urgency

Not enough evidence yet.

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