-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix compiling with separate
jsoo mode
#62
Comments
could you show the stack trace when running a script with |
It doesn't really say anything more. I looked at the compiled output, and at some point there is |
@mitschabaude Does it work for you locally? |
I've added this as a (horrible) work-around to the end of sed -i 's/"port":""/"port":"0"/' "$BINDINGS_PATH"/snarky_js_node.bc.cjs |
Weird stuff! Sorry didn't try locally A while ago we used separate compilation by default, for the released version of snarkyjs. Moved away from it to get smaller JSOO bundle |
It's much faster, but when I try to use it I get this error with a snarkyjs only modified at parts unrelated to this (AFAICT, might be wrong):
The text was updated successfully, but these errors were encountered: