Plans to support for SSG/ISR? #2796

nghiepdev · 2022-04-14T09:46:37Z

nghiepdev
Apr 14, 2022

Hey team,

Are there plans to support SSG/ISR?

sergiodxa · 2022-04-15T03:52:34Z

sergiodxa
Apr 15, 2022
Maintainer

There was a discussion from before v1 here #179

I don’t think there’s an immediate plan from the team to add SSG/ISR support, you could get the same results by using Cache Control headers in your routes, Next’s ISR is a Cache Control with the stale-while-revalidate directive with a custom and vendor lock-in API, while the Cache Control header is standard.

0 replies

jdgamble555 · 2022-11-15T13:27:46Z

jdgamble555
Nov 15, 2022

That discussion link only briefly mentions ISR. This should be added to the Framework, as I believe this is a huge reason certain people would prefer NextJS over Remix.

The Remix Team claims that ISR is vendor-lock-in, but this is simply not true. Netlify, Firebase, Heroku, Cloud Run, Digital Ocean, etc all support ISR on NextJS. Not only that, NuxtJS has added the feature, and Rich Harris has said SvelteKit will have the feature after 1.0.

This is huge as it will not only make revalidation easy (would need an adapter for different environments), but it would save database reads, and be faster.

Please add this ability (or something similar to easily use and revalidate cache-control.

J

3 replies

sergiodxa Nov 16, 2022
Maintainer

Most CDNs have an API endpoint to purge cached responses, that endpoint depends on your CDN and Remix has no opinion on that so you should check yourself what CDN you're using and how to do that. Then you can use Cache-Control to cache forever or enable SWR.

Next.js ISR support outside Vercel doesn't work the same as in Vercel, because in Vercel your static HTMLs are cached in their CDN, when using for example Heroku or Digital Ocean your static HTML files are cached on disk AFAIK. I think only Netlify has added support and it's something specific for Next, ISR is not a feature all frameworks can do regardless of where you deploy.

jdgamble555 Nov 16, 2022

So I would respond to that by asking if Windows makes you "check yourself" on how to install drivers based on your individual hardware?
These days it just installs your drivers for you, and you don't have to think about it. One option would definitely be to put this on the users.

However, a better option would be to create an adapter pattern so that each Hosting Environment Company and environment can create their own adapter that works seamlessly without the user having to think about it. This is what Vercel did with NextJS and will do with SvelteKit. This is how NuxtJS works.

How the CDN stores static files is of little importance compared to the ability to cache them in the first place, and cache them easily because the frameworks handles this well. By putting the standard into the framework, you will open up the door for the framework to prosper among more users.

J

airtonix May 2, 2024

It's a nice idea, and one worth following, but this:

So I would respond to that by asking if Windows makes you "check yourself" on how to install drivers based on your individual hardware?
These days it just installs your drivers for you, and you don't have to think about it. One option would definitely be to put this on the users.

Made me cringe.

A lot of developers use Linux, where you are indeed required to think about these kinds of things.

I think if you're trying to create pressure by comparing common scenarios, then your following statements about how nuxt/next etc work would be enough.

ascorbic · 2024-02-15T09:13:18Z

ascorbic
Feb 15, 2024

I've written a guide on how to do ISR on Remix with normal cache headers. It's not exactly the same as ISR on Next.js, but it gives you all the good bits: on-demand revalidation, TTL, stale-while-revalidate. https://developers.netlify.com/guides/how-to-do-isr-and-advanced-caching-with-remix/