Output file tracing silently discards dependency-resolution failures: build exits 0, deployed standalone output 500s / silently drops page metadata

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-layer file pruning.)

Desired outcome

**Current:** `next build` exits 0 with zero diagnostics, while output file tracing has already hit — and recorded nowhere visible — a dependency-resolution failure. The page's `.nft.json` ends up with a **bare `package.json`** for the broken package: ```bash node -e " const files = require('./.next/server/app/profile/[slug]/page.js.nft.json').files; console.log(files.filter(f => f.includes('lru-cache') && !f.includes('next/dist'))); "

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