fix current_dir() call when using wasm generation
#37
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 is a proposed pr to get the in-browser proof generation example to work locally.
When targetting wasm
create_recursive_circuitcallscurrent_dir().unwrap(). The built wasm which will be packaged will fail to generate the proof, sincecurrent_dir()is not supported in the browser.Also, it could be nice to make
WEBSITE_ROOTa parameter? So that the generated wasm is agnostic to where r1cs and wasm files are located. Will open a PR if this is of interest :)Tangential: the example app seems down as of now?