.NET on WebAssembly - Bindings to Sentry's JavaScript SDK

[bruno-garcia]

The Sentry package as well as the new Sentry.AspNetCore.Blazor.WebAssembly work on the browser through wasm.

Related work:

• [Hackweek] Blazor Wasm SDK #2569
• Make sure Sentry.AspNetCore works with Blazor #317
• feat: Added .NET8 as TFM for Blazor.WebAssembly package #3501

We have a sample in the repo:

• Sample Blazor Wasm #574

But none of the work done yet (other than the draft PR from hackweek have done anything related to bundling our JS SDK.
This should allow us to get Session Replay, our User Feedback Widget as well as some JS specific features like Unhandled Promise Rejections, etc.

Related issues and PRs:

• Blazor - WebAssembly build_id section dotnet/runtime#91049
• WebGL JavaScript & native error handling sentry-unity#668
• Support for Web exports sentry-godot#114
• [experimental/hackweek]: js sdk integration sentry-dart#2238
• feat: add JS Browser support sentry-kotlin-multiplatform#27
• @sentry/wasm will not work if wasm url is a blob url sentry-javascript#8259 (comment)
• fix(wasm): Avoid throwing an error when WASM modules are loaded from blobs sentry-javascript#8263
• Support event caching for Blazor WebAssembly #2291

Package is still -preview, but got some downloads already
Tracking adoption of Blazor specific wasm package: https://nugettrends.com/packages?months=6&ids=Sentry.AspNetCore.Blazor.WebAssembly

[bruno-garcia]

Symbolication is blocked by:

• Emit Producers section when compiling to wasm dotnet/runtime#96334

[MaxwellDAssistek]

This would also be nice to have for Server Interactive Blazor mode.

[bruno-garcia]

This would also be nice to have for Server Interactive Blazor mode.

Are those errors not captured today? if it's a C# error it should already be captured regardless if thrown client or server side. The JS SDK would help capture JS errors that don't get into the C# handler (P/Invoke should).