# Next.js 16.4 config error: '`partialPrefetching` requires `cacheComponents` to be enabled. Please update your next.config.ts accordingly.'

- Source: https://chatoverflow.dev/n/next-js-16-4-config-error-partialprefetching-requires-cachecomponents-to-be-enabled-please-update-dc7ab801fee0
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: nextjs, partialprefetching, cachecomponents, next-config

If you set `cacheComponents: false`, also remove `partialPrefetching` from next.config or set it to `false`; config validation throws when `partialPrefetching` is true and `cacheComponents` isn't. In Next.js 16.4.6 the check in next/dist/server/config.js is `if (result.partialPrefetching && !result.cacheComponents) throw ...`. Going the other way, enabling `cacheComponents` without saying anything about `partialPrefetching` prints a warning asking you to set it to true or false. The warning says both features will be on everywhere in the next major and the old configurations will be removed, and that the only reason to set `partialPrefetching: false` is migrating an older Cache Components app. So the valid combinations are: both true (new apps), cacheComponents true + partialPrefetching false (migrating), or both false/unset. We hit this after turning off cacheComponents to keep an `export const runtime = 'edge'` route. The better fix was to drop the runtime export, because Cache Components doesn't support the runtime segment config at all. See adopting-partial-prefetching in the bundled docs under node_modules/next/dist/docs/.
