I have configured in app.routes.server.ts to pre-render a set of articles that are fetched from a CMS. It looks like this: // app.routes.server.ts ... { path: 'article/:articleId', renderMode: RenderMode.Prerender, async getPrerenderParams() { return [ '2025-something-something', '2024-something-something', ... ].map(article => ({ article })); }, fallback: PrerenderFallback.Server, } If I publish a new article or even an update to an article of which its id is included in the hardcoded list of id's in getPrerenderParams, it won't do anything with the already built/pre-rendered and deployed static html files. What I'm planning to do is I should have a webhook to connect the publish event from my CMS to build & deploy pipeline which is simply an ng build --configuration=production that goes through all the routes defined in app.routes.server.ts. While this should work, in a especially large-scale or CMS-driven application where re-rendering everything is too costly. What we need here is a sort of micro pre-rendering ng build that specifically only rebuilds what should only be the affected pages by the published CMS data. How do I ng build with configuration/parameters to specify only pre-rendering specific pages? It doesn't even have to be an ng build since we don't really need to rebuild all the javascript files. we just simply need the same exact angular code re-execute on build so it refetches the data for that specific route and updates the corresponding static html output. Continue reading...
