Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Default caching in Next 14 vs Next 15

119,220 Aufrufe • vor 2 Jahren •via X (Twitter)

10 Kommentare

Profilbild von Rasmus Hjulskov
Rasmus Hjulskovvor 2 Jahren

More dogs. Check 👍

Profilbild von Alex Sidorenko
Alex Sidorenkovor 2 Jahren

My favorite API

Profilbild von Kain
Kainvor 2 Jahren

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

Profilbild von Alex Sidorenko
Alex Sidorenkovor 2 Jahren

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.

Profilbild von Koka
Kokavor 2 Jahren

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

Profilbild von Augusto Ponce
Augusto Poncevor 2 Jahren

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

Profilbild von Alex Sidorenko
Alex Sidorenkovor 2 Jahren

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

Profilbild von mBAm
mBAmvor 2 Jahren

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

Profilbild von Alex Sidorenko
Alex Sidorenkovor 2 Jahren

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.

Profilbild von aiu
aiuvor 2 Jahren

Wow Amazing. I was really hopping

Ähnliche Videos