Skip to content

fix(appinsights): rename JS initializer to match assembly name - #1

Merged
kolatts merged 1 commit into
mainfrom
kolatts/fix-appinsights-js-initializer-name
Mar 20, 2026
Merged

fix(appinsights): rename JS initializer to match assembly name#1
kolatts merged 1 commit into
mainfrom
kolatts/fix-appinsights-js-initializer-name

Conversation

@kolatts

@kolatts kolatts commented Mar 20, 2026

Copy link
Copy Markdown
Owner

Summary

  • Renames BlazorApplicationInsights.lib.module.jsImagile.Framework.Blazor.ApplicationInsights.lib.module.js
  • Blazor WASM only auto-loads JS initializer files named {AssemblyName}.lib.module.js
  • The old name caused window.blazorApplicationInsights to never be defined, resulting in the runtime error: Could not find 'blazorApplicationInsights.addTelemetryInitializer' ('blazorApplicationInsights' was undefined)

Test plan

  • Deploy to QA/prod, verify no blazorApplicationInsights was undefined error on load
  • Verify telemetry initializer (cloud role/instance tags) appears in Application Insights

@kolatts
kolatts merged commit 04f1c7a into main Mar 20, 2026
1 check passed
@kolatts
kolatts deleted the kolatts/fix-appinsights-js-initializer-name branch March 20, 2026 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant