Загрузка видео...

Не удалось загрузить видео

На главную

Default caching in Next 14 vs Next 15

119,220 просмотров • 2 лет назад •via X (Twitter)

Комментарии: 10

Фото профиля Rasmus Hjulskov
Rasmus Hjulskov2 лет назад

More dogs. Check 👍

Фото профиля Alex Sidorenko
Alex Sidorenko2 лет назад

My favorite API

Фото профиля Kain
Kain2 лет назад

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

Фото профиля Alex Sidorenko
Alex Sidorenko2 лет назад

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
Koka2 лет назад

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

Фото профиля Augusto Ponce
Augusto Ponce2 лет назад

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

Фото профиля Alex Sidorenko
Alex Sidorenko2 лет назад

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

Фото профиля mBAm
mBAm2 лет назад

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
Alex Sidorenko2 лет назад

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
aiu2 лет назад

Wow Amazing. I was really hopping

Похожие видео