Set up J2CL JavaScript build #64
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.
Together with #63 this is my experiment from a couple of days ago described in #58.
If you run
bazel build javascript:dhall(and have a recent-ish version of bazel on your machine), you'll get a JavaScript file inbazel-bin/javascript/dhall.jsthat you can use as described in #58.If we merge this I'll close #58 and we can open new issues for things like refining the JavaScript API and setting up packaging or publishing or whatever.
At some point we might want to run the bazel build in CI, but right now I don't think it's worth the effort. There's a chance we'll accidentally introduce incompatible changes, but they should be easy to identify and fix.