next-runtime
next-runtime copied to clipboard
netlify
Support for on-Demand Revalidation
I'm having issues using the on-demand revalidation when hosted on netlify. When I test it locally by doing next build and next start it works. However, when I test it on a build-deploy or live, it does not seem to update the page.
I have validated that the API endpoint in netlify gets run, has the correct data and unstable_revalidate did not break. (in ___netlify-handler function log)
Does on-demand revalidation not work on netlify yet, or am I missing some config?
EDIT:
Also discussed in https://github.com/netlify/netlify-plugin-nextjs/discussions/1228
Originally posted by iankduffy February 18, 2022 Hello, NextJS 12.1 has added On-demand Incremental Static Regeneration currently in Beta / Unstable, just wondering if in the future if we are looking to add this to netlify plugin?
Hi @kamerat Currently on-demand revalidation is not supported. It is on our roadmap, but we cannot share a date for support yet.
@ascorbic is unstable_revalidate unsupported still? I just tried it and it seems to not work, at least.
@ascorbic Still to this date with [email protected] res.revalidate(), it doesn' t update the page although the revalidate api endpoint handle the request.
@iurage we are keen to support this as soon as possible and are working toward it as per our roadmap
Would be good to hear an update on this. It's been a much talked about feature in my team and we're really looking forward to selling this performance benefit to our clients!
Really would like to see this for feature parity with other hosting providers. Any updates on timeline? This is bordering on dealbreaker for us as we have a massive blog that we can't realistically rebuild every time someone finds a typo.
I'm afraid I can't be any more specific than "this is being worked on". We're waiting on some new platform features that we need for this to work, but I think you'll be pleased with the results.
"this is being worked on"... i mean, seems like a trivial task given that you already support {revalidate: 60}. If you're concerned about resource use, then just paywall it. It wouldn't be so bad if we also didn't have to wait 60 seconds for revalidation... maybe bring that down to 10 seconds?
i mean, seems like a trivial task given that you already support
You know that they there say are the two hard problems in computer science?
It's actively been looked at at the moment, but I can't provide a timeline yet @theooog.
Hey guys, I'm sure you're sick of people asking, but my team is really excited about this feature.
Are there any updates to this? Or maybe a timeframe? Hopefully I'm not adding too much pressure 😄
Probably easier to switch to Vercel at this point.
Guaranteed that right after we switch to Vercel, Netlify will fix this. But growing extremely impatient at the lack of updates on this. Terrible having to manage a NextJS implementation without on demand revalidation.
@orinokai @ascorbic Our team would also love NextJS On-Demand Revalidation supported on Netlify. Looking forward to seeing this released! Do you have a public roadmap where we can follow along with the progress on this feature?
@justynspooner i'm afraid we don't currently maintain a public roadmap, but please be assured it's a priority and we're working hard to get this shipped
+1 - It would be great to get ongoing updates on this feature, it has major impacts to us in project usages / api limits and bandwidths
What are the current pending tasks that need to be completed for this to go live?
Because this is an open-source plugin, we'd like to contribute to it via a public checklist.
It has been more than a year, can we at least get an update and or ETA?
@dev-fredericfox, although it's undocumented, this feature is enabled for Next.js sites on Netlify based on my experience.
Does it work for you?
@charkour Dosen't seem to work for me. Did you get it to work on 13 with the app router? It works fine locally (Next.js 13 App router), and the webhook returns "ok" when on netlify, but the pages do not refresh.
Revalidate does not work for me either (using Next 13 with App Router). My current workaround is to redo deploy with the option "Clear cache and retry with latest branch commit".
@dev-fredericfox, what is your revalidate: <ttl>? For example, my TTL is set to 60 seconds, so even when I run revalidate, my browser will cache the webpage until the TTL is up. Locally, Next.js will immediately update the page (when using next start) but with Netlify, it will start the TTL count the moment the page is loaded (not based on when it was built on the server).
Revalidate on Next.js 13.3 with the Pages Router works on Netlify. You could email Netlify Support asking if there is anything that needs to be "enabled" on your account, but I don't think that's the case.