This has been an issue that I've experienced with various packages built with emscripten since 2019 and honestly surprised it's still there. It's one of the biggest painpoints of working with emscripten + node.js for me personally

import binaryen from 'binaryen'; let s = "testing"; // Desparately trying to debug to figure out what problem is // But this message gets burried in undesired garbage console.log("s = ", s); // Fatal error which makes emscripten print massive unreadable textwall for no discernable reason // filling console and making logs unreadable s(444);

running the above code via node index.js results in the following message (which takes several seconds to print) and appears to be generated by emscripten

I've experienced this exact problem with every emscripten package I've used including internal ones at previous company so I don't think this is the fault of the package maintainers.