vercel/next.js · error

`partialPrefetching` requires `cacheComponents` to be enable

Error message

`partialPrefetching` requires `cacheComponents` to be enabled. Please update your ${configFileName} accordingly.

What it means

`partialPrefetching` controls partial (PPR-style) prefetch behavior that only works when `cacheComponents` is enabled. If partialPrefetching is truthy and cacheComponents is falsy, normalization throws. Checked every phase.

Source

Thrown at packages/next/src/server/config.ts:569

    if (
      result.experimental.turbopackRustReactCompiler &&
      !result.reactCompiler
    ) {
      throw new Error(
        `\`experimental.turbopackRustReactCompiler\` requires \`reactCompiler\` to be enabled. ` +
          `Please add \`reactCompiler: true\` in ${configFileName}.`
      )
    }
  }

  if (result.experimental.cachedNavigations && !result.cacheComponents) {
    throw new Error(
      `\`experimental.cachedNavigations\` requires \`cacheComponents\` to be enabled. Please update your ${configFileName} accordingly.`
    )
  }

  if (result.partialPrefetching && !result.cacheComponents) {
    throw new Error(
      `\`partialPrefetching\` requires \`cacheComponents\` to be enabled. Please update your ${configFileName} accordingly.`
    )
  }

  if (result.experimental.ppr) {
    throw new HardDeprecatedConfigError(
      `\`experimental.ppr\` has been merged into \`cacheComponents\`. The Partial Prerendering feature is still available, but is now enabled via \`cacheComponents\`. Please update your ${configFileName} accordingly.`
    )
  }

  if (result.output === 'export') {
    if (result.i18n) {
      throw new Error(
        'Specified "i18n" cannot be used with "output: export". See more info here: https://nextjs.org/docs/messages/export-no-i18n'
      )
    }

    if (!hasNextSupport) {

View on GitHub (pinned to 0ae8c72462)

Solutions

1. Enable cacheComponents: add `cacheComponents: true`
2. Remove partialPrefetching if cacheComponents is not intended

Example fix

// before
module.exports = { partialPrefetching: true }
// after
module.exports = {
  cacheComponents: true,
  partialPrefetching: true
}

if (partialPrefetching && !cacheComponents) {
  throw new Error('Enable cacheComponents before partialPrefetching')
}

When it happens

Trigger: Setting `partialPrefetching: true` at the top level without also enabling `cacheComponents: true`.

Common situations: Following an older guide that mentioned partialPrefetching as a standalone toggle. Migrating from experimental.ppr and setting partialPrefetching instead of cacheComponents.

Related errors

• `experimental.cachedNavigations` requires `cacheComponents`
• `experimental.ppr` has been merged into `cacheComponents`. T
• Config options `experimental.proxyPrefetch` and `experimenta
• `experimental.useCache` cannot be disabled when `cacheCompon
• Cannot prefetch '${href}' because it cannot be converted to

AI-assisted analysis of vercel/next.js@0ae8c72462 (2026-08-06). Data as JSON: /api/errors/7493763e56fb2481. Report an issue: GitHub.