@alexdotjs @nextjs From what I’ve seen, you have to put that on *every* route module.

@tshddx @nextjs if that's true I ain't migrating

@alexdotjs @nextjs use @remix_run

@imanthonyholmes @nextjs @remix_run

@alexdotjs @nextjs Yeah, in my exp you have to put "force-dynamic" or "force-static" depending of if you want static vs dynamic content. I found automatic detection a pretty bad DX for now. Maybe it could work nice with PPR.

@alexdotjs @nextjs yeah - unfortunately, it's painful. I still don't understand why can't they do a better API design/similar as react query do - do not modify the way I fetch data, instead give me the tools to cache it properly, see more:

@alexdotjs @nextjs there are four different caches and this only disables a couple of them afaik 🙈

@alexdotjs @nextjs this would work. but i think it does not allow you to force dynamic at a lower level. Gonna hit those Vercel function limits quick!

@alexdotjs @nextjs You need it in every page, but yes.

@alexdotjs @nextjs I just put it on every page in case tthe router is trying to be too clever

@alexdotjs @nextjs Wonder if you put that in middleware 🤔

@alexdotjs @nextjs I think you need to add it to every server file.

@alexdotjs @nextjs This will opt in into dynamic mode. Unfortunately you will still run into router (client) cache that invalidates every 30 seconds (for dynamically generated pages) - to fix this you will need to heavily rely on revalidatePath or revalidateTag or router.refresh.

@alexdotjs @nextjs Lamaooo

@alexdotjs @nextjs I did little helper for NextJS data cache (tags or revalidate) which might help in some cases

@alexdotjs @nextjs // <YOU_CANT_FIRE_ME_I_QUIT>

@alexdotjs @nextjs idk, but when I use it, it makes the red go away

@alexdotjs @nextjs You should try @QwikDev