Does it support incremental site generator?

[LorhanSohaky]

No description provided.

[SergeyMyssak]

Hello @LorhanSohaky!

What do you mean by "incremental site generator"?

[LorhanSohaky]

@SergeyMyssak , https://vercel.com/docs/next.js/incremental-static-regeneration

[BlakePetersen]

ISR is just a revalidation strategy, I don't see how it would affect the generation of sitemaps.

Can you provide more information as to what you're looking to achieve?

[LorhanSohaky]

My use case is that I have a huge list of products and blog posts (example "product/1", "product/2", ..., "blog/post1",...). So my idea is that daily I make a request to know if there are new publications and new products.

The requests are relatively expensive so I have to avoid using SSR

[BlakePetersen]

Yep, that definitely makes sense.

I have a similar use case where we aren't full migrated to Next.js and need to include a list of routes from the legacy platforms along with the routes in our static path map. We don't have a massive number of pages so I am going to avoid setting up a cron and fetch that list of routes at build time and drop it into the "include" property array.

I think it makes a lot of sense to grab that list nightly rather than at build if it's a heavy / expensive process.

[LorhanSohaky]

Yep, that definitely makes sense.

I have a similar use case where we aren't full migrated to Next.js and need to include a list of routes from the legacy platforms along with the routes in our static path map. We don't have a massive number of pages so I am going to avoid setting up a cron and fetch that list of routes at build time and drop it into the "include" property array.

I think it makes a lot of sense to grab that list nightly rather than at build if it's a heavy / expensive process.

In my use case every day new pages are created so I would have to do a build every day