Loading video...

Video Failed to Load

Go Home

Default caching in Next 14 vs Next 15

119,220 views • 2 years ago •via X (Twitter)

10 Comments

Rasmus Hjulskov's profile picture
Rasmus Hjulskov2 years ago

More dogs. Check 👍

Alex Sidorenko's profile picture
Alex Sidorenko2 years ago

My favorite API

Kain's profile picture
Kain2 years ago

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

Alex Sidorenko's profile picture
Alex Sidorenko2 years ago

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.

Koka's profile picture
Koka2 years ago

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

Augusto Ponce's profile picture
Augusto Ponce2 years ago

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

Alex Sidorenko's profile picture
Alex Sidorenko2 years ago

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

mBAm's profile picture
mBAm2 years ago

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

Alex Sidorenko's profile picture
Alex Sidorenko2 years ago

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.

aiu's profile picture
aiu2 years ago

Wow Amazing. I was really hopping

Related Videos