Build the trace explorer as a standalone web app - #45
Draft
VojtechStep wants to merge 11 commits into
Draft
Conversation
This makes it easier to reuse when the trace explorer becomes a standalone static HTML document
Options set to their less strict variants are options I'd like to eventually make strict, but it's too much of a bother right now
VojtechStep
changed the title
This file contains hidden or 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
1 participant
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.
Fixes #12 (insofar as building the website, there is no deployment). Builds on #41. The one new commit is f2cecfe.
The visual presentation is still WIP --- the file selection button is just floating around, and the textfield for elpi options shouldn't be there. But I wanted to share how little work is necessary after #41 is merged.
I deployed this version to https://sw.vojtechstep.eu/elpi-trace-explorer/ if you want to play with it. The deployment process is just setting the correct
baseUrlinsrc/ssg/config.jsonand uploading the./distdirectory to a static file host (grebedoc.dev in my case). Not counting sourcemaps and removing the now obsolete functions from the generated trace API, the total bundle is under 300 KB on disk, which is not bad.