@elastic/apm-rum-core incompatible with IE11
See original GitHub issueAt line 164 in dist/lib/common/utils.js
the build is using default parameters, which is not working in IE11.
function getServerTimingInfo(serverTimingEntries = [])
When this @elastic/apm-rum
is included in full bundle/webapp, the whole app/bundle is broken on IE11.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
IE 11 Support - APM Rumjs Issue - Elastic Discuss
Go to RUM - JS tab; Follow the steps 1 and 2 (npm install @elastic/apm-rum --save); Run in localhost and open in IE...
Read more >Transpile the distribution files to ES5 by default #426 - GitHub
We can keep the import/export statements but we should use transpile everything else to ES5. We can also publish source to let bundler ......
Read more >@elastic/apm-rum-core - npm
Start using @elastic/apm-rum-core in your project by running `npm i @elastic/apm-rum-core`. There are 3 other projects in the npm registry ...
Read more >Technology support | Dynatrace Docs
Support includes Server Core installation (requires OneAgent installed in headless-mode) or ... Azure SQL Elastic Pool, Supported database frameworks, yes.
Read more >elastic/apm-rum/package.json - UNPKG
The CDN for @elastic/apm-rum. ... 4, "description": "Elastic APM JavaScript agent", ... 31, "test:e2e:supported": "npm run script runE2eTests ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Apologies for the delay, we are working on a PR to fix this problem and users shouldnt work about running @elastic/* through babel loader. You can check this issue #426
@vigneshshanmugam after explicit changing exclude pattern for babel in webpack (which is normally
node_modules
) it works again. As it still looks like there was a change in@elastic/apm-rum
/@elastic/apm-rum-core
, I would suggest to at least mention this change, and one could argue that such a change to the build should have triggered a major release, as it was a breaking change, which in our case, actually broke the whole of our app, not just the apm integration.