Details about Problem

There is no WebAssembly TFM available in NuGet, which makes the creation of libraries impossible at this point.

This prevent, for instance :

• https://github.com/nventive/Uno.ReactiveUI
• https://github.com/nventive/Uno.Rx.NET
• https://github.com/nventive/uno.mvvmlight
• https://github.com/nventive/uno.prism

from being ported back to their original repositories for reviews and enable proper support for WebAssembly.

This impacts all mono-wasm based projects that needs to have a NuGet ecosystem, as well as mono-wasm itself, for platform specific implementations (e.g. WebSockets, Bindings, etc...)

References

• This PR was closed: TFM mappings for WebAssembly and MonoUE NuGet.Client#2159
• This issue discussed WebAssembly substantially: https://github.com/dotnet/corefx/issues/27417
• This mono PR that deals with nuget: Add WebAssembly framework moniker to NuGet mono/mono#7839
• This .NET Standard issue: .NET Standard for WebAssembly dotnet/standard#1073