IE11 doesn't support template literals
See original GitHub issueWhen using this on IE11 it throws on one of your error:
throw new TypeError(`Cannot perform '${trap}' on a proxy that has been revoked`);
Bundling your library with “production” environment produces the following error:
Error: vendor.js from UglifyJs
Unexpected token: name (lastRevokeFn) [vendor.js:57606,6]
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Template literals syntax is not working in IE11 - Stack Overflow
If you look at the ECMAScript 6 compatibility table, you'll see that template literals are not supported by IE11. The "use strict"; statement...
Read more >Cross Browser Compatibility of ES6 Template Literals ...
ES6 Template Literals (Template Strings) is Not Supported on Internet Explorer 11. If you use ES6 Template Literals (Template Strings) and ...
Read more >JS error in Internet Explorer. Template literals (backtick) not ...
Problem/Motivation The 2.0.2 version of browser_detect.js uses backticks for template literals which is throwing an error in Internet ...
Read more >Template literals (Template strings) - JavaScript | MDN
Template literals are literals delimited with backtick (`) characters, allowing for multi-line strings, string interpolation with embedded ...
Read more >ES6 Template Literals (Template Strings) - CanIUse
"Can I use" provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.
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 Free
Top 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

Can this please be fixed properly? IE11 support is the whole point of using this polyfill - and then you don’t transpile to something IE11 can actually use?!
I ran into the same issue as @wyqydsyq.
Until this is resolved my solution is to include passing the specific node_module through Babel in my webpack config: