Closed zaydek closed 3 years ago
This is mistaken. We’ve already implemented support for caching hydratable pages to __export__
. Seeing as live reload or whatever we end up calling it simply means refresh the JavaScript, not the HTML, this seems to be a mostly solved problem, given we work out the kinks in the existing dev
command. Closing.
Right now we build a page per request which is ideal for hard refreshes but not ideal for live reloads which should be more immediate. This is what Remix Run does.
One of the reasons this is tricky is because whether or not we want to have a cache. Probably the more important concern is whether we can take advantage of incremental recompilation here first. What we want is incremental recompilation and caching visited but unchanged pages.