Support `cacheComponents`

[chargome]

vercel/next.js#84280 moves experimental.ppr to experimental.cacheComponents

We need to at least update our e2e test and make sure the SDK does not break this behaviour.

[linear]

JS-1038

[kevva]

It does break, at least with Webpack/Rspack.

Route "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/some/route" used `crypto.randomUUID()` before accessing either uncached data (e.g. `fetch()`) or Request data (e.g. `cookies()`, `headers()`, `connection()`, and `searchParams`). Accessing random cryptographic values synchronously in a Server Component requires reading one of these data sources first. Alternatively, consider moving this expression into a Client Component or Cache Component. See more info here: https://nextjs.org/docs/messages/next-prerender-crypto

I'm not able to use Turbopack yet because it's missing this crucial feature.

[kevva]

@chargome, anything I can help with here? I think it needs to be handled in here somewhere (or in wrapServerComponentWithSentry) but since everything is synchronous it makes it a bit hard and I don't want to embark on something that you guys aren't aligned with. Maybe you have some plans for this already.

[chargome]

Hey @kevva thanks for reaching out again. We won't fix this in any template code as this will become obsolete for turbopack. The problem lies somehwhere in ID generation, where we need to opt-out of this caching behaviour. I need to dig deeper on this myself first before making any recommendations. It is on my list, I'll keep you updated!