Develop with Wasm GHCI browser mode instead of JSaddle #1404
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See docs.
The stuff in the last commit doesn't work yet for a few reasons. GHCIWatch doesn't work with multiple components (MercuryTechnologies/ghciwatch#316), although I'm close to a workaround for this. Note that GHCID doesn't work at all with the Wasm GHCI browser mode, as discovered a few days ago on the Miso Matrix channel. And anyway, Wasm browser mode doesn't work with multiple components in the first place, as I've just discovered and also raised on Matrix.
Since I collapsed the frontend components together in an earlier commit,
make -f Makefile.wasm32 frontend-watchdoes work, and allows us to get reload-on-save behaviour for changes inprimer-miso. However, this is not much use until the browser mode supports hosting static files, because the Primer app is pretty unusable without its CSS. In the meantime, it'd probably be good to splitMiso.hsin order to speed up reloads.