Next.js 16 + Turbopack with Bun: conflicts, warnings, and production fixes

Upgrading to Next.js 16 with Turbopack often increases warning noise. The right approach is impact-based triage, not blind warning suppression.

Triage model

• P1: runtime/security impact;
• P2: compatibility risk;
• P3: advisory ecosystem warning.

Key cases handled

• non-standard NODE_ENV;
• stale baseline-browser-mapping;
• middleware-to-proxy deprecation migration.
• Package can't be external dependency conflicts with Bun.

Build hygiene

rm -rf .next node_modules
bun install
bun run build

Final takeaway

Reliable migration comes from fixing high-impact warnings first and documenting non-critical noise with scheduled review.

This post is licensed under CC BY-NC.