Native Notify
подписчиков: 8 тыс.
Learn how Caching & Revalidation works with Next.js 13.
NextChat: NextChat.ai
Segment-level Caching Documentation: nextjs.org/docs/app/building-...
Other videos:
Next.js 13 API Route Handlers FULL CRUD: • Next.js 13 API Route H...
NextChat.ai just killed ChatGPT: • NextChat.ai just kille...
#nextjs13 #caching #revalidation
Комментарии: 27
@dawid_dahl +5
I’ve been watching hours of rambling YouTube videos about Next 13 and this was literally the only thing I needed to know. Thank you for explaining it in 4 minutes.
@gmkhussain +7
Senior Engineers: Premature optimization is the root of all evil
@Sulhouse
I seem to be having an issue where the data is being revalidated, however new images that are part of that revalidation aren't, and they come up as broken "The requested resource isn't a valid image /path/to/image received text/html; charset=utf-8" However when I manually refresh the server they seem to work
@Infante1979
This is awsome, thank you so much. You helped me a lot. I found an issue with data caching even using "no-store" and the problem was TURBO. Avoid using this: "dev": "next dev --turbo", in your package.json
@neetdemon
Oh my god dude, thank you! My brain was about to explode trying to figure out how caching and revalidation worked.....
@robertgioeli3211
The only way I’ve gotten this to work is to just make fetch requests to POST() routes in the api folder. If they are GET() requests, it just never refreshes data.
28 дней назад@quangphannhut2777 +1
I'm looking for with 3rd party fetching like Axios, look like I can't implant next revalidate in request. Any help? Thank you so much!
@golden_smiles
It is still doesn't work if you want to get some new data every time on a page navigated to, without reloading the whole your blackjack with everything. The fetch doesn't even hit, and ups, you still have your precios old data on your screen, unless it doesn't 'use client' component.
@user-mf1ft6iz4l
Is that work only refresh time ?
14 дней назад@supermanbrz +4
Why does it not work on route change? This sucks, my users wont be reloading the page.
@sudipta.p.b
Deploying on vercel is worse. It caches all data and no solution mentioned here disables cache. I will check heroku once, else opt out of nextjs altogether
@AdnanKhan-yg4ng
does this next chat has access to 2023 data ? or does he knows everything about next 13 ?
@harshwardhanshetty4683
i am sending response more than 2mb and it's annoying like hell
День назад@mlnima
dude you wast my time, I needed a info about revalidatePath and invalidateTags, please do not share incompleted information on the internet you will confuse beginners
@lunar-ix9vu
Alternatively put, { revalidate: 3 } refreshes if you haven’t refreshed in the last 3 seconds.
28 дней назад