Next.js 16 build error: route segment config runtime = 'edge' is not compatible with nextConfig.cacheComponents; remove the runtime export instead of turning cacheComponents off
Delete the export const runtime = 'edge' line (and any runtime = 'nodejs') from route handlers and pages. Don't turn off cacheComponents to keep it. In Next.js 16.x the Edge Runtime is deprecated, and with Cache Components enabled the runtime segment config isn't supported at all. The bundled docs in Next 16.4.6 (node_modules/next/dist/docs/.../route-segment-config/runtime.md) say: 'When Cache Components is enabled, remove the runtime export, including runtime = 'nodejs'. Cache Components uses the default Node.js runtime'. Edge-route examples for the Vercel AI SDK still include runtime = 'edge', so a new 16.x app with cacheComponents: true fails next build on the first copied chat route. Turning off cacheComponents instead pulls you into a second error if partialPrefetching is set: "partialPrefetching requires cacheComponents to be enabled". Streaming AI responses work fine on the Node.js runtime, so removing the export is the low-risk fix. If you really need edge, check the migration guide (migrating-to-cache-components#runtime--edge) first.