Next 16 - Route segment config "dynamic" is not compatible with nextConfig.experimental.cacheComponents. Please remove it.

[glekner]

What is the replacement for Route segment config? I don't want to enable PPR for all of my routes.

[icyJoseph]

Mmm I think you are looking for https://nextjs.org/docs/app/api-reference/functions/connection

Put it at the opt of the page, that means, don't pre-render past this point, await for a runtime incoming request.

[icyJoseph]

@glekner did you try out await connection()?

[haroonmaqbool]

In Next.js 16, the dynamic route segment config has been replaced by the new static/dynamic rendering model using cache and revalidate.
If you don’t want to enable PPR (Partial Prerendering) for all routes, you can control it per route like this:

export const dynamic = 'force-static'; // or 'force-dynamic'
export const revalidate = 0; // disables caching for fully dynamic routes

The dynamic config isn’t compatible with experimental.cacheComponents, so you’ll need to remove it and rely on these new route-level exports instead. This gives you the same flexibility without enabling PPR globally.

[DanielSalazarLoaiza]

In Next.js 16, the dynamic segment config has been deprecated in favor of the new Partial Prerendering (PPR) model.
When experimental.cacheComponents is enabled, all routes are expected to follow the new caching and rendering semantics.

There’s currently no per-route replacement for dynamic — if you want to exclude certain routes from PPR, the workaround is to disable cacheComponents and handle dynamic rendering manually (e.g., via cache: 'no-store' or revalidate: 0).

The Next.js team is still refining selective opt-out behavior, so finer-grained control may return in a future release.