vercel/next.js · error

Learn more about how to configure Turbopack with Next.js:\nh

Error message

Learn more about how to configure Turbopack with Next.js:\nhttps://nextjs.org/docs/app/api-reference/config/next-config-js/turbopack

What it means

validateTurboNextConfig, after reporting configuration/tools unsupported by Turbopack, logs this warning pointing to the turbopack next.config.js documentation so developers know where to move or replace webpack-era options; hard errors already exit the process with code 1.

Source

Thrown at packages/next/src/lib/turbopack-warning.ts:181

    )

    process.exit(1)
  }

  if (unsupportedConfig.length) {
    unsupportedParts += `\n\n- Unsupported Next.js configuration option(s) (${cyan(
      'next.config.js'
    )})\n  Turbopack will ignore the following configuration options:\n${unsupportedConfig
      .map((name) => `    - ${red(name)}\n`)
      .join('')}`
  }

  if (unsupportedParts) {
    Log.error(
      `You are using configuration and/or tools that are not yet\nsupported by Next.js with Turbopack:\n${unsupportedParts}\n`
    )

    Log.warn(
      'Learn more about how to configure Turbopack with Next.js:\n' +
        underline(
          'https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopack'
        )
    )
  }

  return rawNextConfig
}

View on GitHub (pinned to 0eb3775416)

Solutions

1. Move your webpack configuration to the turbopack config format; see the Turbopack docs for Next.js.

When it happens

Trigger: Thrown at packages/next/src/lib/turbopack-warning.ts:181 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of vercel/next.js@0eb3775416 (2026-08-19). Data as JSON: /api/errors/f0010a03f1243314. Report an issue: GitHub.