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

Upgrading to Next.js 16 with Turbopack increases build speed but can also increase the volume of warnings. The operational mistake is trying to "zero out logs" without prioritizing impact. In this post, I document the method I used to classify and fix alerts without introducing regressions.

Warning classification by criticality#

I separate them into three levels:

1. P1: affects runtime/security (fix immediately);
2. P2: may affect compatibility (fix within a short window);
3. P3: advisory/ecosystem (document and monitor).

Case 1: Node_env conflict#

Inconsistent environment warning:

You are using a non-standard "NODE_ENV" value...

Applied fix:

• remove NODE_ENV from .env;
• let next dev and next build define the mode;
• use a custom variable for the stage:

NEXT_PUBLIC_APP_STAGE=staging

Case 2: Outdated baseline-browser-mapping#

bun add -d baseline-browser-mapping@latest

Case 3: Middleware-to-proxy deprecation#

Deprecation requires care in apps with auth/edge rules. The workflow I apply:

1. validate support of the SDK being used;
2. create a migration branch from middleware -> proxy;
3. test protected routes and redirects;
4. roll out gradually.

Case 4: "Package can't be external" error with Bun#

In projects with a deep dependency tree, Turbopack might fail with:

Package agent-base can't be external...

Workflow that resolved this in my environment:

1. clean cache and locks:

rm -rf .next node_modules bun.lock yarn.lock
bun pm cache rm

1. externalize only parent packages in serverExternalPackages;
2. use resolutions to flatten conflicting versions;
3. run bun pm trust --all and regenerate Prisma when applicable.

Build and cache hygiene#

After structural changes:

rm -rf .next node_modules
bun install
bun run build

This prevents false positives caused by old cache.

Post-change observability#

Minimum validations before production:

• build without fatal errors;
• smoke test of critical routes;
• monitor 4xx/5xx in the first hour;
• rollback path ready in the previous release.

Consolidation notes#

This set of problems belongs to the same family of incidents that also appear in runtime migrations, such as Bun + Next.js or in headless Prisma Studio diagnostics. The difference between a productive project and a fragile project is having a structured triage and rollback strategy.

Production takeaways#

In Next.js 16, maturity is not "eliminating every warning." It is treating first what impacts runtime and security, documenting what is ecosystem noise, and maintaining a predictable correction pipeline without breaking critical routes.

See also

Development Bun, Node.js, and PM2 in production: when to use, when to avoid, and architectural trade-offs

Development Type-safe i18n in react and prisma: validating translation keys at build time with typescript

Development Node.js to Bun: migration with real benchmark, compatibility, and rollback

This post is licensed under CC BY-NC.