vercel
Add Your Reaction Here
Reactions on this comment will be reflected on https://reactions-demo.vercel.app/
This uses Next.js’s Incremental Static Regeneration feature which is supported out of the box by Vercel’s Edge Network.
Data Fetching Code:
https://github.com/chibicode/reactions/blob/42e08310fdbdd370a366bc6cacd043e2636c10c6/pages/index.js#L3-L60
Are you sure its revalidation is done every 1 second or the Github gets updated values after a delay? I get the updated values on the page after a couple of minutes.
Interstingly it updated the first time after a second and a second time after some minutes..
page is not refreshing after1 sec! updated only after few mins..
yes, I tested and same issue with you
So the first request that trigger the incremental build will alway get the stale data?
Is it expected to be updated alone every 1 second without refreshing ? Because I wait 20 Minutes just watching if it will update the information and still not updating
@Abdalhadi-Jarad no, since it's a static page you have a refresh a couple of times to regenerate the page.
Just in case anyone wants to know how this demo behaves with different timeouts, I made a fork and you can see it on https://reactions.jrayo.vercel.app/
Is it expected to be updated alone every 1 second without refreshing ? Because I wait 20 Minutes just watching if it will update the information and still not updating
@zhangfaliang no, since it's a static page you have a refresh a couple of times to regenerate the page.
Great, but I am a little bit confused, doesn't this feature just beg for custom bots to poll the static sites periodically, since the first page served after timeout is stale?
Great, but I am a little bit confused, doesn't this feature just beg for custom bots to poll the static sites periodically, since the first page served after timeout is stale?
@zed-b the page served whilst the timeout is stale displayed a loading or skeleton or blank page whilst the new page is being regenerated.
@chibicode @leerob I think I am missing something. I modified the code (see gist) to print out a given timestamp passed through getStaticProps. I would expect that the page should regenerate every minute, and hence my timestamp shouldn't change during refresh. However, I noticed that when I refresh the page, the timestamp is always updated. thoughts? 🤔
Update: I just realized that during yarn dev getStaticPropstriggers all the time during refresh, but when running fromyarn start`, getStaticProps behaves as it should!
Does anybody know why my reactions are not up to date? I visited the demo app a while ago and it worked. Yesterday I visited it again and noticed the values have not changed since then.
Our GitHub personal access token expired. We'll get a new one added. In the meantime, you can see a similar demo here: https://on-demand-isr.vercel.app/
