gk

Same situation here, very desperate

I got the same issue 🥲

Resolved the issue by overriding the framer-motion version in the pnpm configuration: ```json "pnpm": { "overrides": { ... "framer-motion": "11.15.0" } } ```

Hi @better-salmon we use app router. When the cache is not primed the revalidation goes fast.

@better-salmon how about creating a tags manifest? Something like [this](https://github.com/vercel/next.js/discussions/52203) maybe?

Hi @amannn, thank you for the great work on next-intl! Just to confirm, does next-intl currently not support ~per-page revalidation~ partial prerendering (PPR) for Next 15? Since params are now...

Thanks for the update! Yes, I was referring to partial prerendering (I updated my comment). I would have expected `generateStaticParams` to influence this behavior, and it indeed worked in Next...

I'm uncertain whether `next/root-params` will be supported in server actions in addition to 'use cache.' The current `unstable_rootParams` API does support server actions. If root parameters are not supported, will...