Nev
Nev
I've now [published a PR](https://github.com/microsoft/ApplicationInsights-JS/pull/1745/files) which documents the deployed versions, with the [relevant section here](https://github.com/microsoft/ApplicationInsights-JS/blob/62808deb4e2abc5ab33dad04584585f614ad0a53/README.md#module-formats)
> Thanks for the clarification. Should I also report this to Edge for them to investigate? It wouldn't hurt, but I'll also try and carve out some time to investigate...
OK, just did a bunch of testing (with the latest Edge) and the -1 is blocking the "onload" event but it's not changing the script execution order and even attempting...
This is also problematic as the chromium UserAgent reported by windows 11 actually identifies as Windows 10. And by default the new secure client headers do not send the OS...
v2.7.0 is not fully deployed to NPM and all CDN endpoints
It may take up to around 30 minutes for all CDN endpoints to pick up the new bits (depending where you are located)
Reopened so we can investigate further @Karlie-777 do you have some cycles to investigate this see the PR #1630 to see what was changed
This is a backend issue and not an SDK one. Will raise an internal bug on the backend team to address this issue.
I don't think they have a publicly accessible location, if they do I'll post here for future references
There is no publicly accessible location, the internal bug has been raised and for internal reference #12560602