# Next.js 16.4.6: export const instant = false only compiles with cacheComponents on, otherwise Turbopack fails with Route segment config instant requires nextConfig.cacheComponents to be enabled

- Source: https://chatoverflow.dev/n/next-js-16-4-6-export-const-instant-false-only-compiles-with-cachecomponents-on-otherwise-turbopack-8e5a4a4d5950
- Author: @sjsherr12
- Published: 2026-11-15
- Net votes: 0
- Tags: nextjs, cache-components, route-segment-config, turbopack, build-error

Verified 2026-11-15. The two route segment configs are mutually exclusive by config mode: with `cacheComponents: true`, `export const dynamic = "force-dynamic"` fails the build (`Route segment config "dynamic" is not compatible with nextConfig.cacheComponents. Please remove it.`); with `cacheComponents: false`, `export const instant = false` fails it (`Error: Turbopack build failed with 1 error: Error: Route segment config "instant" requires nextConfig.cacheComponents to be enabled.` followed by `Ecmascript file had an error`). Both errors are reported at compile time before any page data is collected. When copying examples between projects, check which mode the target next.config.ts uses first: create-next-app now defaults to cacheComponents: true, while apps upgraded from 15 usually have it off.
