Skip to content

fix(appinsights): explicitly import JS module to fix undefined blazorApplicationInsights #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kolatts merged 1 commit into from
Mar 21, 2026
Merged

fix(appinsights): explicitly import JS module to fix undefined blazorApplicationInsights #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions src/Imagile.Framework.Blazor.ApplicationInsights/Components/ApplicationInsightsInit.razor.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,13 @@ protected override async Task OnAfterRenderAsync(bool firstRender)

ApplicationInsights.InitJSRuntime(JSRuntime);

// Explicitly import the JS module to ensure window.blazorApplicationInsights is defined.
// The .lib.module.js auto-loading mechanism is not reliable for NuGet-distributed RCLs,
// so we import it explicitly here before making any interop calls.
await JSRuntime.InvokeAsync<IJSObjectReference>(
"import",
"./_content/Imagile.Framework.Blazor.ApplicationInsights/Imagile.Framework.Blazor.ApplicationInsights.lib.module.js");

if (Config.Config != null)
{
try
Expand Down
Loading