A page re-rendering and page deletion composable

[chibx]

Describe the feature

This request is for the implementation of a renderPage() method capable of calling the internal prerender process of Nuxt to render, not just normal pages, but those with dynamic slugs.
I believe this feature would prove significant for blogs, and various static sites to control the re-rendering of specific pages upon update to their respective data.

export default defineEventHandler(async (event)=>{
  await renderPage('/posts/24', { query1:  'mostLiked' });
});

The previous way of adding prerenderable slugs below results in the the need to rebuild to get fresh new routes/slugs:

import { ofetch } from 'ofetch';

const getPlanetsRoutes = async () => {
    const response = await ofetch("https://api.nuxtjs.dev/planets");
    return response.map((planet) => `/planets/${planet.slug}`);
}

export default defineNuxtConfig({
    hooks: {
        async 'nitro:config'(nitroConfig) {
            const planetsRoutes = await getPlanetsRoutes();
            nitroConfig.prerender.routes.push(...planetsRoutes);
        }
    }
});

This feature request prevents the need for unnecessary rebuild and allows re-rendering to occur server-side. This will improve flexibility and ease as anyone could cache a page based on data/[slug title] gotten from a database.
Developers will be able to delete pages that are no longer needed (maybe after deletion of data from a store) using removePage(route).

The feature would be added only for users with the prerender feature enabled on at least one route, so as to avoid rendering conflicts with a full SSR app rendering mechanism

Additional information

• Would you be willing to help implement this feature?
• Could this feature be implemented as a module?

Final checks

• Read the contribution guide.
• Check existing discussions and issues.

[kc-fantasy]

Yes, I need that feature, too。dynamically update some static prerender pages

[danielroe]

cc: @pi0

[Spreizu]

Until (and if) this feature ever lands, is there a workaround to tell Nitro to prerender the pages to a file when the preset is set to "node-server" or maybe even "nitro-prerender"? Even if we ignore the deletion part. Like.. maybe using the "x-nitro-prerender" header to tell Nitro to prerender these pages and save them to a file?

I think the most annoying thing about all of this is the fact that the server can not be bundled in a CI/CD environment and needs a full Node runtime & all of the dependencies, for example, to prerender pages (which it can do on runtime, while being 100x smaller in size if bundled).