You said a single page app without React, so just vanilla JS? Are you just loading in an HTML file, or are you hoping for some type of dev server with hot reloading that will also bundle the site?
Heh, I actually wrote multi-page application 
In my case, my goal is to have an interactive tutorial for data structures and algorithms, kinda like what Red Blob games do. So concretely, I aim to have something like this:
- A single, shared .js bundle that contains dependencies and shared logic
- One .js file per page
- The HTML page (either hand-crafted or generated by something else) have a couple of divs with IDs that the application hooks into and replaces
I’d like to have hot reloads of at least the CSS, though I think just normal automatic reloads of the others is what I can get with ReScript – …but perhaps there’s some way to distinguish state and rendering logic inside a ReScript app that means I can, at dev time, only reload the rendering logic?
That’s very particular for my problem though. What I’d like is more of a general tutorial that can help me on my way to get to such a setup, or make me realise if this is not recommended at the moment. I’ve seen Getting started | Experimental WebAPI which says “Experimental”, so maybe I’m a bit early to the party.