chore(deps): update dependency @microsoft/applicationinsights-web to v3

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@microsoft/applicationinsights-web	^2.8.7 → ^3.4.3

---

Release Notes

microsoft/ApplicationInsights-JS (@​microsoft/applicationinsights-web)

v3.4.3

This is a maintenance release for the 3.4.x version line adding a new SDK statistics feature, a PostChannel reliability fix, and dependency security hardening. The @microsoft/1ds-post-js channel is numbered 4.4.3 and requires v3.4.3.

Significant Changes (since 3.4.2)

• Customer SDK Stats: Added a new SdkStats feature that periodically collects internal SDK usage/health statistics. It is enabled by default and can be disabled (or explicitly configured) via the featureOptIn configuration (e.g. featureOptIn: { SdkStats: { mode: FeatureOptInMode.disable } }); the collection interval defaults to 15 minutes (sdkStats.int).

• PostChannel Auto-Flush Stall Fix: Fixed a permanent stall in @microsoft/1ds-post-js where, under sustained intermittent send failures (e.g. a load balancer returning occasional 503s), auto flush could wedge behind the flush() wait-for-idle timer and permanently stop draining the in-memory queue — causing telemetry to be silently dropped as QueueFull until the process was restarted. Auto flush is now fire-and-forget and no longer parks the scheduler waiting for the manager to become completely idle.

• Dependency Security Hardening: Pinned tar to >=7.5.16 to remediate CVE-2026-53655 and resolved the remaining npm audit findings in build tooling via dependency overrides (js-yaml, yaml, markdown-it, linkify-it). These are build/tooling changes and do not affect the published runtime packages.

Changelog

• #​2746 Fix PostChannel auto-flush permanent stall under sustained intermittent send failures
• #​2745 fix(security): pin tar >=7.5.16 to remediate CVE-2026-53655
• #​2707 Enable Customer SDK Stats
• Resolve remaining npm audit findings via dependency overrides (js-yaml, yaml, markdown-it, linkify-it)

Full Changelog: microsoft/ApplicationInsights-JS@3.4.2...3.4.3

v3.4.2

This is a maintenance release for the 3.4.x version line containing security hardening, bug fixes, build tooling improvements, and CI updates. The @microsoft/1ds-post-js channel is numbered 4.4.2 and requires v3.4.2.

Significant Changes (since 3.4.1)

• Prototype Pollution Hardening: The extend() and objExtend() helpers now filter unsafe keys (__proto__, constructor, prototype) to prevent prototype pollution when merging untrusted objects.

• Dependency Vulnerability Resolution: Migrated the repository from npm to pnpm for dependency management and resolved all known dependency vulnerabilities. This is a build/tooling change and does not affect the published runtime packages.

• OsPlugin Field Name Correction: The OsPlugin now emits the correct Common Schema 4.0 field names (ext.os.name and ext.os.ver). Telemetry consumers relying on the previously emitted (incorrect) field names should update to the corrected names.

• RequestEnvelopeCreator Envelope Name Fix: Fixed RequestEnvelopeCreator so request telemetry is sent with the correct envelope name (Microsoft.ApplicationInsights.{ikey}.Request) instead of RequestData.

• Offline Channel Reliability: Fixed a missing return after reject() in the offline channel that could lead to a null provider dereference.

• Fixed [INVALID_ANNOTATION] warnings in Rolldown / Vite 8 consumers (#​2736): The per-module dist-es5 output (the package module entry that modern bundlers import) emitted parenthesized PURE tree-shaking annotations with whitespace after the opening parenthesis (e.g. ( /*#__PURE__*/"http.")), which stricter bundlers such as Rolldown (Vite 8) rejected. The build now canonicalizes these annotations to the flush form ((/*#__PURE__*/"http.")) in the dist-es5 output, accepted by all bundlers while preserving the wrapping parentheses required for older Rollup / Webpack / Terser to tree-shake the constants. This complements #​2737, which only normalized the rollup-bundled dist/es5 (main) output.

CI / Tooling

• Dropped Node.js 16 from CI matrix: Node.js 16 is End-of-Life and several dependencies (e.g. puppeteer, @pnpm/error) now require Node.js 18 or later. The CI pipeline no longer runs against Node.js 16.
• Added Node.js 22 and 24 to CI matrix: The CI pipeline now tests against Node.js 18, 20, 22, and 24.
• Migrated from npm to pnpm: Dependency management now uses pnpm.

Changelog

• #​2733 fix: Migrate from npm to pnpm and resolve all dependency vulnerabilities
• #​2742 fix(ci): repair Node.js CI (Chrome install, bundle-size limits, ts-async offline-channel hang)
• #​2737 fix: remove invalid PURE literal annotations and add bundle validation tests
• #​2736 fix: canonicalize PURE annotations in dist-es5 (module) output to fix Rolldown/Vite 8 [INVALID_ANNOTATION] warnings
• #​2735 fix: prevent prototype pollution in extend() and objExtend() via unsafe key filtering
• #​2734 fix(offline-channel): Add missing return after reject() to prevent null provider dereference
• #​2732 fix(OsPlugin): use correct CS 4.0 field names ext.os.name and ext.os.ver
• #​2731 Drop Node.js 16 from CI matrix; add Node.js 22 and 24
• #​2729 Potential fix for code scanning alert no. 2273: Workflow does not contain permissions
• #​2728 Potential fix for code scanning alert no. 5940: Unused variable, import, function or class
• #​2727 Potential fix for code scanning alert no. 5402: Semicolon insertion
• #​2726 Potential fix for code scanning alert no. 5401: Unused variable, import, function or class
• #​2725 Potential fix for code scanning alert no. 4240: Semicolon insertion
• #​2724 fix: RequestEnvelopeCreator sends "RequestData" as envelope name instead of "Microsoft.ApplicationInsights.{ikey}.Request"
• #​2722 Update Components
• #​2721 Add CfgSync documentation

Full Changelog: microsoft/ApplicationInsights-JS@3.4.1...3.4.2

v3.4.1

Compare Source

This is the first full supported release of the 3.4.x version line. While a 3.4.0-beta was previously released for early testing and validation, version 3.4.0 was not released as a standard supported version — 3.4.1 is the first production-ready release in this series. The @microsoft/1ds-post-js channel is numbered 4.4.1 and requires v3.4.1.

Significant Changes (since 3.3.11)

The following are the significant changes since the previous full release (3.3.11). Some of these changes were previously included in the 3.4.0-beta release.

• W3C Trace State Support: Added full support for managing W3C Trace State and sending headers in distributed tracing, including new distributed tracing modes AI_AND_W3C_TRACE and W3C_TRACE that enable the tracestate header to be sent with requests when trace state information is available, the existing states will continue to not send the header.

• New Distributed Tracing Modes: Added new eDistributedTracingModes enum values:

  • AI_AND_W3C_TRACE (17): Sends Application Insights headers + W3C traceparent + W3C tracestate headers (if state value is present)
  • W3C_TRACE (18): Sends only W3C traceparent + W3C tracestate headers (if state value is present)

• Enhanced Distributed Tracing: Refactored the distributed tracing implementation to provide better support for the W3C Trace Context specification and prepare for future OpenTelemetry Span-style API integration.

• New W3C TraceState API: Introduced the IW3cTraceState interface that provides a mutable, ordered list of key/value pairs for trace state information with proper parent-child relationships.

• OpenTelemetry Integration Preparation: Added foundational OpenTelemetry interfaces (IOTelSpanContext, IOTelTraceState) to provide OpenTelemetry API compatibility.

• Additional Configuration: Added new configuration properties for W3C trace state support:

  • traceHdrMode: Controls if the SDK should look for the traceparent and/or tracestate values from service timing headers or meta tags from the initial page load (in IConfiguration)
  • Enhanced distributedTracingMode property to support the new W3C trace state modes (in ICorrelationConfig)

• Dependencies Extension: The dependency tracking extension now includes additional logic for W3C trace state handling, which may affect custom dependency listeners or initializers. The following interfaces and functions have been enhanced with W3C trace state support:

  • IDependencyListenerDetails interface now also includes a readonly traceState along with the previous traceId, spanId, traceFlags properties
  • addDependencyListener() function now provides access to W3C trace state information through the enhanced details object
  • addDependencyInitializer() function continues to work with existing dependency telemetry processing
  • Custom dependency listeners can now access and modify W3C trace state information before requests are sent

• Enhanced Cookie Management: Cookie values are now cached in memory when cookies are disabled instead of being lost, enabling support for consent banner workflows where cookies must be temporarily disabled until user approval. Automatic flushing occurs when cookies are re-enabled.

• OsPlugin Reliability Improvements: Improved OsPlugin with proactive OS retrieval, unload handling, and session caching for more reliable OS detection.

• URL Redaction Enhancements: Made URL redaction more dynamic for improved flexibility in field redaction scenarios.

Package Deprecation

The following packages have been merged into @microsoft/applicationinsights-core-js and are now deprecated. They continue to be published as backward-compatible shims (re-exporting from Core) so existing code will not break, but they are no longer used as dependencies by the main SDK packages. You should stop importing from these packages and migrate to @microsoft/applicationinsights-core-js directly.

• @microsoft/applicationinsights-common — All exports have been merged into @microsoft/applicationinsights-core-js. The package is now a compatibility shim that re-exports from Core. See the Migration Guide for details on updating your imports. This package will be removed in a future major release (4.0.0).

• @microsoft/1ds-core-js — All exports have been merged into @microsoft/applicationinsights-core-js. The package is now a compatibility shim that re-exports from Core. See the 1DS Core Migration Guide for class/import name changes and migration steps. Consumers should update their imports to reference @microsoft/applicationinsights-core-js directly. This package will be removed in a future major release (4.0.0).

Breaking Changes

The following is a list of known breaking changes for anyone attempting to implement the interfaces, for end-users / consumers of the existing interface this is considered to be only a potential breaking change as the existing functions are still provided and provide the same level of functionality. The breaking nature of these changes is for anyone attempting to provide their own implementation of these changes.

Interface Changes

• The IDistributedTraceContext interface has been significantly expanded to include W3C trace state management capabilities, which may affect custom telemetry processors that interact with distributed tracing context.
  • Added additional "required" property accessors which update ONLY the current trace context instance and DO NOT update any parent context instances (pageName, traceId, spanId and traceFlags).
    • The previous set functions continue to also update (replace) any parent context values for existing backward compatability, but have been marked as depracted and will be removed in a future release due to their side-effects of overwriting the parent values.

Potential Breaking Changes

• Class Removal: The TelemetryTrace class has been removed and is no longer exported as part of the distributed tracing refactoring, with its functionality integrated into the new W3C trace state implementation.

  • The properties telemetryTrace is now a complete adpater to the existing core.getTraceCtx() value and as such is now marked as deprecated and will be removed in a future release.
  • The value of the appInsights.context.telemetryTrace is no longer an instance of this removed class.

• Trace Context Initialization: Due to the distributed tracing refactoring, the core instance and SDK will now always have a valid traceId available through core.getTraceCtx(). The traceId will be either a newly generated random value or inherited from any detected parent trace context. This ensures consistent trace context availability but may affect applications that previously relied on the absence of a traceId to determine if distributed tracing was active.

• Dependencies Extension - ajaxRecord Class Removal: The internal ajaxRecord class has been removed and is no longer exported from the dependencies extension (@microsoft/applicationinsights-dependencies-js). The internal implementation now implements the new IAjaxRecordData interface. This class was previously used internally for AJAX request tracking and was referenced in the IInstrumentationRequirements.includeCorrelationHeaders() function signature. Important: The previous exporting of the ajaxRecord class was unintentional and was never meant to be part of the public API - it was an internal implementation detail that inadvertently became accessible to external code.

  • Previous Signature: includeCorrelationHeaders(ajaxData: ajaxRecord, input?: Request | string, init?: RequestInit, xhr?: XMLHttpRequestInstrumented): any
  • New Signature: includeCorrelationHeaders(ajaxData: IAjaxRecordData, input?: Request | string, init?: RequestInit, xhr?: XMLHttpRequestInstrumented): any
  • New Interface: The IAjaxRecordData interface has been introduced to replace the ajaxRecord class in public API signatures and provides access to essential AJAX request properties:
    • getAbsoluteUrl(): string | null - Gets the absolute URL for the request
    • getPathName(): string | null - Gets the sanitized path name for the request URL
    • traceCtx: IDistributedTraceContext - The distributed trace context for the request
    • requestHeaders: { [key: string]: string } - Object containing request headers
    • aborted?: number - Indicates whether the request was aborted
    • context?: { [key: string]: any } - Optional context object for dependency listeners
  • Impact: This change only affects custom implementations that directly referenced the ajaxRecord class or implemented the IInstrumentationRequirements interface. Standard SDK usage and most custom dependency listeners/initializers are unaffected.
  • Migration: If your code previously referenced ajaxRecord or implemented IInstrumentationRequirements, update it to use the new IAjaxRecordData interface, which provides the same essential properties with proper TypeScript definitions and comprehensive JSDoc documentation.
  • Need Help?: If you discover that your code depends on other functions or properties from the dependencies extension that are no longer exported and you believe should be part of the public API, please raise an issue with details about your use case so we can review and potentially provide a proper public API alternative.

• Flush Method Signature Change: Renamed flush method parameter from async to isAsync in IChannelControls interface to avoid potential keyword conflicts (only affects code that relies on named parameters).

  • Fixed return type of flush method to properly include boolean when callbacks complete synchronously

Potential behavioral changes

This release enhances the cookie management behavior when cookies are disabled. Previously, when cookies were disabled, calls to cookieMgr.set() would return false and cookie values would be lost. Now, these operations are cached in memory and automatically applied when cookies are re-enabled to allow for cookie compliance banners and delayed approval.

Behavior changes:

• cookieMgr.set() now returns true when cookies are disabled (because values are cached), instead of false
• cookieMgr.get() now returns cached values when cookies are disabled, instead of empty strings
• cookieMgr.del() operations are now cached and applied when cookies are re-enabled
• Applications can now recover cookie state after temporary cookie blocking scenarios

These changes improve data persistence and are considered enhancements rather than breaking changes. If your application logic depends on the previous behavior of set() returning false when cookies are disabled, you may need to check cookieMgr.isEnabled() instead, or configure disableCookieCache: true in your cookieCfg to maintain the previous behavior.

Known Limitations

• SDK Loader (Snippet) automatically downgrades to v2.x on Internet Explorer: When the SDK Loader detects that Internet Explorer is being used (via the msie or trident/ user agent strings), it automatically rewrites the CDN URL to load the v2.x SDK instead of v3.x (e.g. ai.3.gbl.min.js becomes ai.2.gbl.min.js). This means any v3.x-only APIs — including the new OpenTelemetry-based APIs — will not be available for users on Internet Explorer. If your code uses these newer APIs, you should check for their existence before calling them. This fallback does not apply when using the NPM package directly.

Changelog

• #​2719 Improve OsPlugin reliability: proactive OS retrieval, unload handling, and session caching
• #​2718 Address issue with the AppInsightsExtCore using the wrong version number
• #​2716 Make URL Redaction more dynamic
• #​2712 [Main] Merge 1ds-core-js into applicationinsights-core-js
• #​2710 [Main] Merge Trace API Features from Beta
• #​2628 Fix flush method root cause - handle async callbacks in _doSend with proper error handling
  • Potential breaking change: Renamed flush method parameter from async to isAsync in IChannelControls interface to avoid potential keyword conflicts (only affects code that relies on named parameters)
  • Fixed return type of flush method to properly include boolean when callbacks complete synchronously
  • Fixed root cause where _doSend() couldn't handle asynchronous callbacks from preparePayload() when compression is enabled
  • await applicationInsights.flush() now works correctly with compression enabled
  • Added proper error handling and promise rejection propagation through async callback chains
  • Improved handling of both synchronous and asynchronous callback execution patterns
  • No polling overhead - uses direct callback invocation for better performance
• #​2631 [Feature] Update the ICookieMgr implementation to write cookies after being enabled
  • Enhancement: Cookie values are now cached in memory when cookies are disabled instead of being lost, enabling support for consent banner workflows where cookies must be temporarily disabled until user approval
  • Enhancement: Automatic flushing occurs when cookies are re-enabled via setEnabled(true) or dynamic configuration changes
  • Enhancement: Added disableCookieDefer configuration option to maintain backward compatibility with previous behavior (defaults to false)
  • Behavior change: cookieMgr.set() now returns true when disabled (cached) instead of false
  • Behavior change: cookieMgr.get() now returns cached values when disabled instead of empty strings
• [Beta] Add W3c Trace State support / handling and refactor distributed trace handling to prepare for OpenTelemetry Span style API / management

Full Changelog: microsoft/ApplicationInsights-JS@3.3.11...3.4.1

v3.3.11

Compare Source

Changelog

• #​2642 Separate BeaconSendFailure and BeaconSendFailure from SizeLimitExceeded
• #​2675 Fix offline channel recovery for Offline -> Online (#​2674)
• #​2666 Fix unload() to return promise when called without parameters
• #​2667 Add a check to prevent non-string URLs from being passed to fieldRedaction method

Infrastructure changes

• #​2684 Fix minor issue with E2E test
• #​2681 Add redact URL configuration in readme
• #​2676 Fix Flakey Ajax test which has race condition
• #​2670 Fix static web CDN test assertion (Fixes failing CI tests)

Web snippet 1.2.3 (November 10, 2025)

• #​2659 [Web-Snippet] [BUG] @​microsoft/applicationinsights-web-snippet Fix Snippet Loader Error

v3.3.10

Compare Source

Interface changes

This release includes:

• Support for custom providers for Offline Channel which has added customProvider and customUnloadProvider interfaces to the IOfflineChannelConfiguration.
• IAnalyticsConfig is exported for Analytics extension.
• redactUrls and redactQueryParams are added to IConfiguration to support URL redaction.

Changelog

• #​2649 [Main][Task] 2792261: Provide Custom Provider Under Web Worker for Offline Channel
• #​2638 [Main][Task] 3447059: Update Async Tests Under Dependencies Extension To Use the Modern AsyncQueue Pattern
• #​2637 [Main][Task] 3447059: Update AISKU Async Tests To Use the Modern AsyncQueue Pattern
• #​2636 Fix TypeError in Click Analytics Data Collector
• #​2633 Fix flush method root cause - handle async callbacks in _doSend with proper error handling
• #​2632 [Feature] Implement cookie caching when disabled and automatic flushing when enabled with backward compatibility option
• #​2625 Add Azure API Management proxy documentation to FAQ sections
• #​2607 Update Async Tests Under AISKULight to Use the Modern AsyncQueue Pattern
• #​2597 Fix TypeScript compatibility issue with ITelemetryPlugin interface
• #​2595 Fix trackPageView not resetting maxAjaxCallsPerView counter
• #​2583 Create IAnalyticsConfig interface to properly define AnalyticsPlugin configuration subset
• #​2625 Add Azure API Management proxy documentation to FAQ sections
• #​2627 Add weekly GitHub action to delete closed and merged branches
• #​2635 Fix issue #​2634 moving the conditional check for filtering
• #​2549 Redacting urls before sending to telemetry data
• #​2622 Suppressed credentials inline to avoid credscan false positive

v3.3.9

Compare Source

This release contains an important fix for a change introduced in v3.3.7 that caused the autoCaptureHandler to incorrectly evaluate elements within trackElementsType, resulting in some click events not being auto-captured. See more details here.

Changelog

• #​2556 Update SDK Loader to rename the snippet postfix file to avoid CodeQL scanning issues
• #​2586 [AI][Task] 3324697: Update Readme on Error Handler
• #​2581 Export ICorrelationConfig interface from dependencies extension
• #​2587 Click Analytics - Fix capturning of HTML events

v3.3.8

Compare Source

This release contains an important fix for a change introduced in v3.3.7 that caused a ReferenceError exception to be thrown when running in strict mode. See more details here.

Changelog

• #​2524 Update Components to address governance issues
• #​2536 Fix ReferenceError in Click Analytics v3.3.7 by reordering variable declaration
• #​2530 Add negative isArray check to _isConfigDefaults

v3.3.7

Compare Source

Potential breaking change

This release contains a potential breaking change due to the new compress api feaure added. If you are using a Proxy to redirect your telemetry to your own endpoint or are relying on the events to be uncompressed (this feature is initially disabled and it is intended to be enabled by the service in the near future), it is recommended to either update collection endpoint to support GZip or to explicitly disable the feature. See more details here.

Changelog

• #​2518 Remove Generated docs from the repo
• #​2514 Address issues with isFeatureEnabled changes
• #​2517 Update Components to address governance issues
• #​2501 [Main][Task]31233527:Change Default RequestSizeLimitBytes
• #​2507 [main] Handle race condition during unload
• #​2513 [Main][Task]32698211: Add a Config to Allow Users to Change Max Number of Events Per Batch
  • Note: New Config maxEvtPerBatch is added to the post channel IChannelConfiguration.
• #​2511 [Main][Task]31233527: Add a Config to Allow Users to Change RequestSizeLimitBytes
  • Note: New Config requestLimit is added to the post channel IChannelConfiguration.
• #​2506 Drop correlation header to be passed on the dependency
  • Note: Option to drop the enrichment of correlation header during dependency processing is added to DependencyListenerFunction
• #​2504 [main] [Click analytics] not logging no native html input elements
  • Note: trackElementTypes is added to IClickAnalyticsConfiguration to allow additional, configurable HTML element types to be tracked in addition to the default set
• #​2451 [main] enable compress api in 1ds-post-channel and applicationinsights-channel
  • Note: Using compress api feature is added through feature flag zipPayload and is currently disabled by default. See how to enable this feature and more details.
• #​2489 [main][stats beat] implement stats beat in application insights

v3.3.6

Compare Source

Changelog

• #​2481 [Main][Task]31338239: Add Config to allow excluding the configuration endpoints from being reported
• #​2486 Minification improvements

v3.3.5

Compare Source

Changelog

Issues

• #​2430 [BUG] Type signature for stopTrackEvent is incorrect
• #​2442 [BUG] [Snippet] Unhandled exceptions are reported twice
• #​2470 [BUG] @​microsoft/applicationinsights-channel-js lacks a proper repository URL
• #​2467 [BUG] The regex used to parse the stack trace appears to be skipping anonymous lines
  • This fixes the portal missing stack frames which are from anonymous functions due to missed parsing of stack frames with unexpected formatting.

Commits

• #​2428 [main] [snippet] Integrate 1DS with AI Snippet Generation
• #​2443 Update Stale Issue action
• #​2445 [main] snippet generation fix for pr #​2428
• #​2446 [main] eliminate warning raised by tsdoc
• #​2447 [main] [debug plugin] upgrade manifast to v3
• #​2450 [main][doc] Type signature for stopTrackEvent is incorrect #​2430
• #​2448 [main] fix tsdoc error for param and type tag
• #​2452 [main][fix] rush fix
• #​2459 [Main][Task]30499129: Turn on CDN Deprecation Message with Sampling Rate with 10% Each Day
• #​2458 URGENT ACTION: Stop using az416426.vo.msecnd.net
• #​2460 [ThrottleMgr] Turn on Test CDN Deprecation Message with Sampling Rate with 100% Each Day
• #​2461 Update config version to 1.0.1
• #​2463 [main][cfgsync] update test based on new config setting
• #​2462 [main][debug tool] fix the way of calling chrome storage and add new url
• #​2464 Update Code Owners
• #​2465 [main][debug tool] enable check compressed data
• #​2468 [Main][Task]31041354: Increase CDN Deprecation Message Sampling Rate to 20%
• #​2471 [Main][Task]31111291: Fix Repo links in package.json
• #​2455 [main] fix rush warning message
• #​2473 Update rush version

v3.3.4

Compare Source

Changelog

• #​2426 [Main][Task]29626594: PerfManager Should be Created without Customized CreatePerfMgr Function
• #​2421 [Main]: Make file size checks flexible for nightly/dev builds
• #​2434 [Main][Task]29884493: Add a Function to Export Offline Listener From Sender
• #​2437 [Main][Task]29519727: Better Handle Sender Dynamic Changes
• #​2438 [Main][Task]29445623: Update CfgSync Config Readme
• #​2439 [BUG] Sourcemap load errors in debugger from dependencies
• #​2429 Readme - Remove double negative

v3.3.3

Compare Source

Changelog

• #​2401 [Main][Task]28966399: Separate critical events and non-critical events for Offline Support
  • Note: New Config splitEvts is added to Offline Channel Config. By enabling it, offline events will be batched and saved separately based on persistence level
• #​2413 [Main][Task] 2944563: Fix Promise Initialization Sender Config Issue
  • Note: the issue ApplicationInsights Channel (Sender) endpoint Url Promise is Always Pending is resolved
• #​2416 [Main][Task]29519574: Update AISKU Light to better handle Init Promise
• #​2418 [Main][Task]29465842: Update Promise Initialization Post Channel
• #​2404 [main] fix expCfg to be optional
• #​2407 [main] Custom Trusted Type Policy Support for Snippet Script Injection
• #​2409 [main] Trusted Type Policy Support for nounce tag

v3.3.2

Compare Source

Changelog

• #​2396 [Main] Update generated typedoc documentation
• #​2397[Main] Change tslib peerDependency from "*" to open range
• #​2391 [Main] enhance exception telemetry with customer log Information
  • Note: Config expCfg is moved from IConfig to IConfiguration(this change is going to cause the TypeScript type error).

v3.3.1

Compare Source

Interface changes

This release includes:

• Support for custom providers for Offline Channel which has added customProvider and customUnloadProvider interfaces to the IOfflineChannelConfiguration.
• IAnalyticsConfig is exported for Analytics extension.
• redactUrls and redactQueryParams are added to IConfiguration to support URL redaction.

Changelog

• #​2649 [Main][Task] 2792261: Provide Custom Provider Under Web Worker for Offline Channel
• #​2638 [Main][Task] 3447059: Update Async Tests Under Dependencies Extension To Use the Modern AsyncQueue Pattern
• #​2637 [Main][Task] 3447059: Update AISKU Async Tests To Use the Modern AsyncQueue Pattern
• #​2636 Fix TypeError in Click Analytics Data Collector
• #​2633 Fix flush method root cause - handle async callbacks in _doSend with proper error handling
• #​2632 [Feature] Implement cookie caching when disabled and automatic flushing when enabled with backward compatibility option
• #​2625 Add Azure API Management proxy documentation to FAQ sections
• #​2607 Update Async Tests Under AISKULight to Use the Modern AsyncQueue Pattern
• #​2597 Fix TypeScript compatibility issue with ITelemetryPlugin interface
• #​2595 Fix trackPageView not resetting maxAjaxCallsPerView counter
• #​2583 Create IAnalyticsConfig interface to properly define AnalyticsPlugin configuration subset
• #​2625 Add Azure API Management proxy documentation to FAQ sections
• #​2627 Add weekly GitHub action to delete closed and merged branches
• #​2635 Fix issue #​2634 moving the conditional check for filtering
• #​2549 Redacting urls before sending to telemetry data
• #​2622 Suppressed credentials inline to avoid credscan false positive

v3.3.0

Compare Source

Potential breaking change

This release contains a potential break change due to enhancing the definition of the IConfiguration to support Promise types for the connectionString, instrumentationKey and endpointURL; any extension that relies on these base interfaces will VERY likely cause TypeScript to fail with potential warnings about the types being different.

Changelog

• #​2371 Bump @​microsoft/rush from 5.97.1 to 5.129.6
• #​2340 [Main][Task]27939476: Initialization with iKey and endpoint to be promises

!! potential breaking changes. IConfiguration support Promise types for the connectionString, instrumentationKey and endpointURL

• #​2366 [Sdk Loader] Increase version to 1.2.0
• #​2367 [main] update the way to generate ajax perforamance mark prefix

v3.2.2

Compare Source

Changelog

• #​2356 [Main][Task]27488189: Modify offline support enums for isolated mode
• #​2357 [Main][Task]28050373: Expose Offline Support SendNextBatch function
• #​2358 [Main][Task]27080650: Initialization Should Handle Offline Support Dependency
• #​2362 [Main]Publishing: Add support for Az Modules instead of AzureRM Modules
• #​2360 set script attribut to avoid race condition when multiple sdks are inited

v3.2.1

Compare Source

Changelog

• #​2333 [Main][Task]27749889: Change AISKU Sync Mode to Receive
• #​2335 [Main][Task]27681441: Fix async tests for MsAzure Migration
• #​2338 [Main][Task]27923018: Post Channel getOfflineSupport should set correct headers and url based on payload data
• #​2342 [Main][Task]27923018: 1ds post getOffline support url fix

v3.2.0

Compare Source

!! CfgSync plugin is turned on. Throttling Ikey depreciation message is enabled with sampling rate 0.0001%
##​2317

!! Sender has breaking changes. The key used for session storage is changed and items stored in the storage now contain retry counts.
##​2324

Changelog

• #​2371 [Main][Task]27365739 Turn on Ikey depreciation message with sampling rate 0.0001%
• #​2319 [Main] Fix config release script overwrite flag and cache time
• #​2321 [Main] Default request headers content-type for 1ds should be x-json-stream only ing
• #​2324 [Main][Task]27079894 Add a max retry count for Sender
• #​2325 [Main][Task]25716927: Change default CfgSync values to turn on the ikey deprecation message
• #​2331 [Main] Resetting the DataCacheHelper version number back to current version (from 3.0.5)
• #​2332 [Main][Task]27742145: Change nonOverrideCfgs to be added only during initialization
• #​2333 [Main][Task]27749889: Change AISKU Sync Mode to Receive

v3.1.2

Compare Source

!! Critical Bug fix for Memoery Leak !!
#​2311

It also contains a packaging fix for webpack #​2307 (caused by [#​2306]](#​2306) ) and

Changelog

• #​2307 ApplicationInsights-JS latest version 3.1.1 giving TypeError: Cannot read properties of undefined (reading 'getCrypto')
• #​2306 [BUG] Circular dependencies
• #​2311 [BUG] Excessive memory usage for SPA where unload hooks keep accumulating
• #​2299 [Main][Task]27156360: Add json config cdn details to tool folder
• #​2308 [Main][Task]27221819: Remove node 14 (from ci.yml)

v3.1.1

Compare Source

Changelog

• #​2296 [BUG] remove 403 as a “retriable” error code
• #​2276 Update api-docs (typedoc) with the current 3.1.0 release details
• #​2281 [Main][Task]26681188: Handle endpoint url change for offline channel and add notification mgr
• #​2282 Addng two new PII Kind values for IPv6 scrubbing and dropping data.
• #​2285 [Main][Task]25693679: Extract common sendPost implementation for online and offline sender
• #​2197 [main] [BUG] using EndPointUrl (and IngestionEndpoint) results in Telemetry sent to incorrect urls
• #​2288 [Main][Task]27064950: Add doc on adding offline support channel
• #​2295 [Main][Task]27064983: Update post channel to use sender post common interfaces from core
• #​2290 chore: remove extraneous console log from debug plugin

Web snippet additional update to 1.1.2 (March 1st, 2024)

Refer to #​2284 [Web-Snippet] [BUG] @​microsoft/applicationinsights-web-snippet version 1.1.1 type problem

Web snippet additional update to 1.1.1 (Feb 16th, 2024)

Refer to #​2277 [Web-Snippet] dependency chain issues

v3.1.0

Compare Source

Interface changes / Breaking changes

This release includes support for a new Offline Channel which has changed the IChannelsControls interface to include additional support for the new offline channel. This change is to support the new

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.