13 ms·
Interesting, thanks very much. To clarify, the headless chrome is because it's ultimately a js-rendered app, so you just pre-render all the routes on the serve
by nchmy 2y ago
Interesting, thanks very much.
To clarify, the headless chrome is because it's ultimately a js-rendered app, so you just pre-render all the routes on the server to get the final html, cache that, then serve the html on any first request. Then when the app is loaded in the browser, it just does everything client-side?
- holoduke 2y agoIndeed. Thats how it works. Of course when your website is pure html you can simply return the html content. No need to go through a headless browser.