Artyom Sovetnikov

> Would you be open to including the polyfill for `getGlobal` anyway? If it'll solve the issue, sure. I've already tried doing that actually, but it didn't work, because we...

I've tried replacing `this` to `window`, but it returned `Uncaught TypeError: dotnet.HelloWorld is undefined`. Regarding angular, do you mean it's not related with the browser-es sample? In this case we'd...

I'm also not against dropping UMD target if there is a way to make it work with both CommonJS (require) and ES (import) in all the environments. Other UMD scenarios...

> If I were to do it, I would just write it all as an ES module and then polyfill it (like Babel) if needed. The thing is we have...

> WASM that is not in use should be destroyed. Yeah, I felt that way as well, but as mentioned it throws an error on exit. Maybe something on the...

I've tried it again, but looks like `emscripten_force_exit` has been removed since I've last tested this. Not sure what's the correct way to shutdown/dispose the mono runtime now.

Given `emscripten_force_exit` is not exported, mono is probably built without the exit flag. Not sure if it's possible to terminate by other means. https://emscripten.org/docs/api_reference/emscripten.h.html#c.emscripten_force_exit

Right, so it's actually built with no exit flag: https://github.com/Elringus/DotNetUMD/blob/6807d5ceeb52f9421802985d3737479406c95b08/src/mono/wasm/wasm.proj#L67 Guess that means it can't be directly disposed. We could override the flag in our custom branch, but due to...

It's .NET runtime for wasm, which is not just for blazor, so there's still a chance. They've already made a lot of progress to modularize it in .NET 6-7. And...

Hi, Those come from .NET runtime's auto-generated JS wrapper. We currently have to use a modified version of 6.0 runtime (due to #20) and are patching the wrapper to resolve...