We are currently using a custom .NET runtime build and JS wrapper post-processing to support webpack UMD target. This limits the options when building the projects, such as AOT and module trimming.

There is an on-going work at the .NET runtime main branch to modularize the WASM runtime and make it work outside of browser, eg:
dotnet/runtime#61313
dotnet/runtime#62292
dotnet/runtime#47336

At some point, it may become possible to use the module distributed with the runtime SDK, which will resolve the limitations.

If someone happen to know an alternative solution to make current (.NET 6) WASM compatible with UMD target, please let us know here. Sharing updates regarding changes in the .NET runtime that could help with the issue is also appreciated.

Currently blocked by:

• Allow for a way to ensure some source generators run before / after others dotnet/roslyn#57239 (via Migrate to the new JS interop layer #75)
• [browser] Support for web extension constraints dotnet/runtime#80045
• [browser] Provide "single-file" deployment dotnet/runtime#86162