Replace hot reload mechanism #211
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR has two goals:
mesopCLI hot reload's hacky mechanism #199.ibazelandmesopCLI. This way if we break one, particularly for themesopCLI, we will feel the pain right away as framework developers.This creates a new HTTP endpoint "/hot-reload" that the Mesop client app long polls against. If "/hot-reload" returns a 200 (OK) HTTP response this means the Mesop server has finished re-executing the changed modules, then the Mesop client app triggers a hot reload request.
As a nice side-effect, this avoids the ibazel livereload mechanism which is somewhat hairy and relies on this pre-compiled JS file.
Fixes #199.
Note: this will require downstream updates.