User Story: Developers can easily use NuGets with native libraries to build fast wasm projects

[marek-safar]

Developers would like to be able to easily consume NuGets for use in browser-wasm applications. NuGets which consist of managed libraries only are generally supported as long as they target net5.0+ and avoid APIs marked with the [UnsupportedOsPlatform("browser")] attribute. We need to go beyond that and support NuGet packages that include also native/unmanaged code targeting browser-wasm RID.

Work Items

• NuGet Packaging
  • Document structure expectations
  • ABI versioning
  • Source builds
• Tooling
  • Tooling installation (emscripten SDK)
  • Expose version requirements with LTS considerations
  • Run pinvoke generator on NuGet assemblies
  • Relink runtime with native code in build and publish ([wasm] Add support for native relinking after Build, and AOT after publish #57556)

[jkotas]

Potentially related NuGet/Home#9631

[danroth27]

Specific libraries with native dependencies that we've heard customer interest in include SkiaSharp and Sqlite.

[mattleibow]

Has there been any updates to this? I see the other AOT issue is pretty long now :)

[radical]

Has there been any updates to this? I see the other AOT issue is pretty long now :)

I'm working on this.

[raju-kumar]

Good to note this is being worked on. This will help us to utilize skiasharp rendering in browser. Looking forward to see this feature in a preview.

[jeromelaban]

I've gone down that path for Uno, if you want to reuse the findings to include in the runtime: https://github.com/unoplatform/Uno.Wasm.Bootstrap#webassembly-module-linking-support, particularly the part with the multi-versioning of emscripten-targets.

[Xyncgas]

hi

[Xyncgas]

came from #5466 dropping in to get notified

[artemiusgreat]

Why was this moved to Triage?
At the moment Blazor doesn't have any JS-free charting tool with acceptable real-time performance.
Availability of SkiaSharp would be a life-saver.

[lewing]

We're still working on some details but the baseline functionality is in.

[jeffhandley]

@lewing Is this issue ready to close for 6.0.0?

[mairaw]

should this issue be removed from the .NET 6 project?