Update dependency @microsoft/applicationinsights-web to v3.3.3 #105
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/microsoft-applicationinsights-web-3.x
branch
from
af7dd81
to
ff70ac7
Compare
renovate
bot
changed the title
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.0.5->3.3.3Release Notes
microsoft/ApplicationInsights-JS (@microsoft/applicationinsights-web)
v3.3.3Changelog
splitEvtsis added to Offline Channel Config. By enabling it, offline events will be batched and saved separately based on persistence level2944563: Fix Promise Initialization Sender Config Issuev3.3.2Changelog
expCfgis moved fromIConfigtoIConfiguration(this change is going to cause the TypeScript type error).v3.3.1Compare Source
Changelog
expCfgis available to provide more details of exception telemetry. See more details herev3.3.0Compare 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
!! potential breaking changes. IConfiguration support Promise types for the connectionString, instrumentationKey and endpointURL
v3.2.2Compare Source
Changelog
v3.2.1Compare Source
Changelog
v3.2.0Compare 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
v3.1.2Compare Source
!! Critical Bug fix for Memoery Leak !!
#2311
It also contains a packaging fix for webpack #2307 (caused by [#2306]][https://github.com/microsoft/ApplicationInsights-JS/issues/2306](https://github.com/microsoft/ApplicationInsights-JS/issues/2306)6) ) and
Changelog
v3.1.1Compare Source
Changelog
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.0Compare Source
Interface changes / Breaking changes
This release includes support for a new Offline Channel which has changed the
IChannelsControlsinterface to include additional support for the newofflinechannel. This change is to support the newofflinechannel and is a breaking change for any custom channels that implement theIChannelsControlsinterface. If you have a custom channel that implements theIChannelsControlsinterface you will need to update your implementation to include the newofflinechannel.Configuration default changes
As this is a minor version bump we have also change some default values for the following configuration options:
disableUserInitMessageis nowtrueby default to disable the user init message.Potential breaking change
This release contains a potential break change with 'tags' type change
While the interface changes are breaking changes, the changes are not expected to affect the majority of users as when the code attempted to serialize the
tagsproperty it would have failed due to theTags[]type being used instead of the correctTagstype.Old
New
New Offline Channel
This release also includes the new
offlinechannel which is a new channel that is designed to support offline scenarios. Theofflinechannel is designed to store telemetry items in local storage and then send them when the user comes back online.To take full advantage of the initial version you will need to implement your own IOfflineListener to handle situations where you may have "network" connectivity but not internet access. As the
navigator.onLineproperty if available will only tell you if you have network connectivity and not internet access.Changelog
disableUserInitMessagetotrue(was previously false since adding)v3.0.9Compare Source
!! Critical Bug fix for Memory Leak !!
#2311
It also contains a packaging fix for webpack #2307 (caused by [#2306]][https://github.com/microsoft/ApplicationInsights-JS/issues/2306](https://github.com/microsoft/ApplicationInsights-JS/issues/2306)6) ) and
Changelog
What's Changed
Full Changelog: microsoft/ApplicationInsights-JS@3.0.8...3.0.9
v3.0.8Compare Source
This release changes the new beacon splitting code (added in 3.0.4) to be
disabledby default. This change is to address the issue where the SDK was splitting the payload into multiple requests when the payload size exceeded the maximum allowed size for a single request. This issue was introduced in the 3.0.4 release and only affects thesendBeaconusage during page unload, it does not affect thefetchusage during page unload. This change is to address the issue where the SDK was splitting the payload into multiple requests when the payload size exceeded the maximum allowed size for a single request. This issue was introduced in the 3.0.4 release and only affects thesendBeaconusage during page unload, it does not affect thefetchusage during page unload.Changelog
v3.0.7Compare Source
Changelog
This release is a hotfix for issue #2216, which is simular to the issue fixed in
3.0.6but for thefetch(with the keep-alive flag).Changelog
v3.0.6Compare Source
This release fixes an issue with the
sendBeaconusage during page unload, where the SDK was not correctly splitting the payload into multiple requests when the payload size exceeded the maximum allowed size for a single request. This issue was introduced in the 3.0.4 release and only affects thesendBeaconusage during page unload, it does not affect thefetchusage during page unload.Changelog
Configuration
📅 Schedule: 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.
This PR was generated by Mend Renovate. View the repository job log.