Resolve the binaryen uncaught exception wall of text problem

[lastmjs]

These issues will provide context. We are currently using the --abort-on-uncaught-exception flag with tsx as a workaround, which prints an unfortunate native stack trace instead of a wall of text. It would be great to completely resolve the problem.

Issues:

• Huge wall of text printed on uncaught exceptions in Node.js AssemblyScript/binaryen.js#94
• 5.8mb contents of obfuscated wasm module printed when exception thrown elsewhere in program nodejs/node#43462
• entire source of module printed when nodejs exception thrown emscripten-core/emscripten#17228
• Broken sourcemap in the stack trace of uncaught errors privatenumber/tsx#447