⬆️ Use Remix v2 (Classic Compiler) (2)

[agoose77]

This PR builds upon #408 and actually switches to Remix V2, using the classic remix compiler. A future PR would need to be used to pull in the Vite compiler.

This PR doesn't try to fix the problem with static exports.

[agoose77]

@rowanc1 can you elaborate on the redirect bug you saw? Was it for deployed static sites rather than those run from npx serve locally?

[rowanc1]

If you npx serve the built html, landing on any page would go into an infinite reload loop. It is very obvious.

It may only be the case if you change the base path?

E.g. BASE_URL=/_build/html

And then serve from the project directory.

The json that remix sends us seen to be invalid, because we changed it, and then it goes into a loop. Possible that that has been fixed as we are skipping many versions.

[agoose77]

I can confirm that I'm seeing the continuous loop behaviour that you reported for 1.1.18 in version 2.x. It looks like we might need to consider the other routes to static exports (like SSG SPA that I linked previously).

[rowanc1]

Very unfortunate. :(

[agoose77]

I have a stupid idea for upgrading to v2 before we have implemented SSG - mpa-spa. Could we run the MyST server at the same base path such that the hydrated document matches the SSR?

[rowanc1]

Maybe? I think that would be just changing the request coming in (i.e. _build/html/slug) and then in the loader ensuring that matches.