cacheComponents, dymanic rooute and client JS disabled

[mblandr]

So, problem is clear
BEFORE cacheComponents dynamic routes works totally ok with client JS disabled. Ya, we have no interactivity but at least get full html content.
BUT. With cacheComponents now dynamic contents are always STREAMING, streaming NEEDS client JS, so NO CLIENT JS - NO STREAMED CONTENT. And user will only see static shell.
Very nice, isn't it, but is there a solution?
Thanks

[mahirliy55]

I faced a similar issue when disabling client JS on dynamic routes.
In my case, ensuring export const dynamic = 'force-static' and moving fetch calls to server components fixed the cache mismatch.
It seems Next.js reuses static HTML when no use client directive exists.

[mblandr]

1. Route Segment Config is incompatible with cacheComponents, according to docs
   2)didn't understand, sorry - force-static convert ALL route to static