Default caching in Next 14 vs Next 15

More dogs. Check 👍

My favorite API

Why not use <Image>? and does it also works with this cache?

No reason not to use <Image>. I'm just minimizing the code for the demo to make it less visually overwhelming. The Image works as before.

What does becoming static at build means? Is it complex to switch from next14 to 15 for our existing app?

Do you know if cache (unstable_cache) from next will be available? That'd be a solution to supabase db fetching

I'm not sure when it becomes stable. What problems do you have with supabase fetching?

thank you and the next team for all the work you do. but that's works only on dev mode, the issue persist (next 15) after i build the app , I need to add // export const dynamic = "force-dynamic" // same as next-14

By default, Next tries to generate routes statically during the build time. It's a design decision- "static by default, dynamic on demand" Previously, it could be hard to tell if the page was static or dynamic with the app router. Now we have an indicator.

Wow Amazing. I was really hopping