You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This library's emscriptem code sets up an uncaughtException listener at the top level if it is imported.
This handler will re-throw the error, causing the logging to print the exception source line as the minified single line of the project. So importing this library and then having an error will cause a big
This is probably a duplicate of emscripten-core/emscripten#11532 and emscripten-core/emscripten#14270, could you try to add -sNODEJS_CATCH_EXIT=0 -sNODEJS_CATCH_REJECTION=0 to the linker invocation? Note that this requires at least Node v15 to work properly.
So I think if the configuration adds those two parameters then this library will no longer include that exception handler.
The text was updated successfully, but these errors were encountered:
Alright, created a PR that locally worked as expected. Would definitely appreciate a merge + a release of this change, as right now my stack traces are very hard to read without this
This library's emscriptem code sets up an
uncaughtException
listener at the top level if it is imported.This handler will re-throw the error, causing the logging to print the exception source line as the minified single line of the project. So importing this library and then having an error will cause a big
^ you can see the issue running this in node. The stack trace just dumps the entire file.
This seems to be related to emscripten-core/emscripten#17228 and this specific part of the source
From that issue:
So I think if the configuration adds those two parameters then this library will no longer include that exception handler.
The text was updated successfully, but these errors were encountered: