Next.js 12.1: Introducing On-Demand Incremental Static Regeneration

[@uidotdev]

🙏 Great work everyone.

[@whyredvince]

Nice stuff. A video on using React 18 features in NextJS would be awesome!

[@ezekieeeeel]

Looking forward to this. having issues using Suspense atm. Patiently waiting for docs 😁

[@Sdqumar]

In demand regeneration is what any jamstack developer will every wish for❤️❤️❤️

[@jacobsfletch]

This is exactly what we needed. THANK YOU

[@MaxProgramming]

These killer NextJS features make me not go anywhere else 😍

[@naveenbollepalli4440]

A really awaited feature from Next.js 👌

[@AngeloMichel]

Absolute heroes 👍 - great work on all the updates now and lately. Love working with next!

[@Wardret]

Yaaay some love to styled-components !

[@euanmorgann]

Would On demand ISR work for a dynamic path? Say you had a bunch of dynamic paths using getStaticPaths and then wanted to regenerate one specific page would it work the same?

[@jahkoor.a]

Next is such a beast. Love it, so easy to use.

[@PaulFWatts]

Very exciting new feature

[@tomihq]

Love it. I was looking for this out there:)

[@joostjansky28]

💡 This update is HUGE! Thanks 🙏🏻🙏🏻🙏🏻

[@hamidmouad829]

Mind blowing ! great job ! Still one simple feature that I want to be implemented in in Next.js that is type checking in local development even if it reduces the speed locally

[@katech6020]

your IDE can do that using TS language server

[@collinthomas6288]

Omg thank you; this came at a perfect time

[@lucaswong98]

Hi Lee, I'm using a different backend using C# instead of building backend in the Nextjs api folder, at the same time I am self-hosting the project outside of Vercel. Can I still use this feature?

[@albinsjolin649]

Works great for my clients!

[@avidworkslol]

This is such a game changer.

[@thedevsouvik]

I love you sir for the update

[@themoonly]

I have already a java backend hanging on /api and have to define a page under /api for this feature. How can I mix them. Using different names? It could be misleading and strange to understand.

[@oiojin831]

clear explanation!! great product!!

[@lucadifazio2735]

Hi, I am not able to participate in the survey. When I click on the link it tells "thank you for participating" without me actually having taken part of it

[@0xJoey]

This is a game changer

[@andrewkorin]

yay, thanks guys

[@markokraljevic1590]

is there Dockerfile example for 80% smaller image?

[@ZEL0D]

Thank you so much 🙏🏻

[@geisonmcd]

I wrote this exact same code and res.unstable_revalidate('/') doesn't work, it only works when passing the exact route as parameter unstable_revalidate

[@dennisgonzales9521]

lets go !!

[@centereddev]

This is super cool. When are we going to have image optimization at build time? This is pretty much the only thing keeping me on Gatsby.

[@ahnaftahmid7743]

OH YEAH BABY THANKS

[@jenslindstrom2841]

Nice

[@anggoran7398]

If there is on demand ISR, why we still need SSR since we can get new data more efficient? Sorry I'm new to Next js

[@ignaciofedorenco600]

Revalidation doesn't work when i build and start the server

[@davidtbeechey]

Awesome!!!

[@tawsifkamal88]

Woohhooooooo

[@stephen_x]

👍

[@showbikshowmma3520]

how to fetch data without reloading the site thats what i want to know

[@liamwinterton7370]

As someone getting into next.js now, what use cases does this have?

[@JorenMathews]

It lets you update static pages without rebuilding the entire site. If nothing else, that's a lot faster.

[@niclas.horstad]

If your app is based on data from a Content Management System, and someone updates the page, now the CMS can tell Next.js to re-create a static version of that page with the updated content.

[@beqa2758]

I dont understand revalidate was already there for months if not years Altho that unstable* function is new (I think...)

[@persioberberian1716]

The issue is that you could not control when to revalidate the information, lets say you have a blog post where you update every week or so, but once you post something, you want it to appear instantly, how would handle that revalidate time before? Make it like 60 minutes? Having unecessary processing for something that only updates once a week? or make it days and once you publish something, you'd have to wait days for it to appear? Now you can just call unstable_revalidate once a new content is published, and never revalidate it again until next content is up!

[@ms77grz]

👍👍

[@Danny-zf2wu]

res.unstable_revalidate is remove

[@tomascarignano5002]

🥵

[@keshav8497]

I want this persons job ... Technical high paying but still not technical.

[@niclas.horstad]

Why is the function called "unstable_revalidate"?

[@thesunabsolute]

Because it’s not ready for production yet. It may take another year before these features make it into a stable build. They are letting us play with these features so we can give feedback.

[@destroyerYT-d4s]

#642