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
Hi, this is a great project and it would theoretically revive my current obsolete project that have been broken on recent upstream of emcc/clang. Running old emscripten still worked but I can't afford to build everything from source just to run my project, making a static version of emception for my project would be a great solution for this problem. But even though this project will just run as is on node with the QuickJS compiled down, would it be faster to directly passtrough node command to the environment and if possible, to turn off Asyncify/Emterpreter so the whole compiling process will be much faster (but the latter is I guess, more complex than swapping out QuickJS, since I red somewhere in this repo that before you are actually have make a simple passtrough to the browser's JS, it would be beneficial to re-use that capability on node right?)
The text was updated successfully, but these errors were encountered:
Hi, this is a great project and it would theoretically revive my current obsolete project that have been broken on recent upstream of emcc/clang. Running old emscripten still worked but I can't afford to build everything from source just to run my project, making a static version of emception for my project would be a great solution for this problem. But even though this project will just run as is on node with the QuickJS compiled down, would it be faster to directly passtrough node command to the environment and if possible, to turn off Asyncify/Emterpreter so the whole compiling process will be much faster (but the latter is I guess, more complex than swapping out QuickJS, since I red somewhere in this repo that before you are actually have make a simple passtrough to the browser's JS, it would be beneficial to re-use that capability on node right?)
The text was updated successfully, but these errors were encountered: