Is there a way to unite exported functions under the same object path? about tinygo

[aykevl]

I think you're misunderstanding how WebAssembly modules work.
You can import functions given a module + function name, such as (env, addNumbers).
You can export a function with a particular name, such as addNumbers. You can also export it with extra characters in there, so that the function name becomes env_addNumbers, env::addNumbers, env.addNumbers, or anything you like. There's nothing special about that dot, it's just a function name.

Specifically here:

As I mentioned, the JS-clue shouldn't know about exported methods and it should just copy all methods from a particular export section, e.g.:

// Copy all exported methods in "env" object 
go.importObject.env = { ...guestMod.instance.exports.env }

It doesn't work like that. There are no named export sections, just one (unnamed) section with exported functions. You can export addNumbers (or env.addNumbers or whatever), but it's a plain old function name.
Perhaps you can try using Developer Tools and inspect the Module object manually? That may give a better idea of how it works.

[tkhametov]

Thanks for the explanation, @aykevl! I appreciate your help!
Now I understand your point. I realized that there's a new target wasm-unknown in new releases that drastically reduces the emitted functions and generates a pure module without any dependencies. It looks like I can leverage that to implement what I need. Thanks