I’ve been watching hours of rambling TH-cam videos about Next 13 and this was literally the only thing I needed to know. Thank you for explaining it in 4 minutes. Subscribed.
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
I have a revalidate on the api in the next object but it still never refreshes... does my api need to be called in page.jsx? I have my api in an api folder that I import and just call the function from the page.jsx file and I never get a revalidate
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
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.
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.
Yeah I'm making a new video that is coming out next week that fixes this bug too with client components. I don't think I like Next.js 13 anymore personally lol hopefully all the bugs are officially worked out by 14. I don't know.
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
No it doesn't. The solution NextChat.ai has is the global prompt library that has up to date information to that can be used in a conversation to teach NextChat.ai the new way of doing things
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
I've been making videos as the changes happen. I made this video before revalidatePath was a thing. In a future video I talk about revalidatePath. Be mad at Next.js 13 for all their drastic changes all the time, not me lol 😂😂
![⭐ฮิตในTikTok!! ( หมูเด้ง MooDeng ) Ver. แดนซ์โจ๊ะๆ ReMix BY [ ดีเจกิต รีมิกซ์ ]](http://i.ytimg.com/vi/3krsyfWUeHU/mqdefault.jpg)
I’ve been watching hours of rambling TH-cam videos about Next 13 and this was literally the only thing I needed to know. Thank you for explaining it in 4 minutes.
Subscribed.
I'm glad it helped!
Senior Engineers: Premature optimization is the root of all evil
NextJS Team: Let’s cache EVERYTHING
Lol I hate the caching by default more than anything about Next.js 13.
The rubbish pisses me off
Oh my god dude, thank you! My brain was about to explode trying to figure out how caching and revalidation worked.....
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
Bro you just saved my life. I've been facing this issue for some days. Tried StackOverflow but to no avail. Aapne Jaan bacha di!
I hope it's not causing any issues during production
Why does it not work on route change? This sucks, my users wont be reloading the page.
You may be experiencing another problem I talk about in this video: th-cam.com/video/TZXMT-EG7Ak/w-d-xo.html
I have a revalidate on the api in the next object but it still never refreshes... does my api need to be called in page.jsx? I have my api in an api folder that I import and just call the function from the page.jsx file and I never get a revalidate
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!
Is that work only refresh time ?
So I wandering how to revalidate move on Navi to Navi action
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
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.
Me too. I had to switch all my GET requests to PUT requests to fix this in the end.
Thanks sir
cache:no-store is not working for me
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.
Yeah I'm making a new video that is coming out next week that fixes this bug too with client components.
I don't think I like Next.js 13 anymore personally lol hopefully all the bugs are officially worked out by 14. I don't know.
i am sending response more than 2mb and it's annoying like hell
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
You can try this: th-cam.com/video/TZXMT-EG7Ak/w-d-xo.html
The new video above shows how I fixed caching in production
does this next chat has access to 2023 data ? or does he knows everything about next 13 ?
No it doesn't. The solution NextChat.ai has is the global prompt library that has up to date information to that can be used in a conversation to teach NextChat.ai the new way of doing things
Alternatively put, { revalidate: 3 } refreshes if you haven’t refreshed in the last 3 seconds.
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
I've been making videos as the changes happen. I made this video before revalidatePath was a thing. In a future video I talk about revalidatePath.
Be mad at Next.js 13 for all their drastic changes all the time, not me lol 😂😂
I am not mad at you,I solved my issue on revalidatePath by using experimental serverActions and now love it@@NativeNotify