Use native JS backend #137
Draft
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
|
I'd be curious to know what isn't working with the JS backend. If you still remember. |
|
No, sorry, I don't remember where I got stuck. Do you want to try? |
|
Possibly, but I haven't used Nix for a long time, so first I have to figure out how the JavaScript backend works there. |
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.
It seems with GHC 9.8 we no longer need the separate GHCJS project. Yay!
Since NixOS/nixpkgs#208947 the JS backend is available in nixpkgs. Unfortunately, not everything works already, and also plenty of libraries have annoying upper bounds on
basehere. So maybe I’ll park this for a while.