Wasm vs Wasm2js export naming is incompatible

With Wasm2js generating valid ES modules, some information about export names is lost making Wasm modules and their Wasm2js counterpart non-interchangeable.

For example, if the Wasm module exports a function named hello#world, this will be exported as-is in Wasm but as hello_world in Wasm2js output.

Now one could argue that the mangling is necessary to make ES modules in the first place, and another person could argue that compatibility of the resulting module instance is more important. I'd personally favor the latter, since AssemblyScript uses export names (which do allow such symbols by the spec) to transport information about what is an instance method as part of the export's name (like MyClass#myInstanceMethod vs MyClass.myStaticMethod).

Any thoughts?

Start by reproducing the hello#world export example in both a Wasm module and its Wasm2js output, then compare the resulting export names. The issue is resolved when equivalent module instances preserve compatible export names, including names containing #, or when the project documents an agreed alternative.