Promise polyfill not working on IE11
See original GitHub issueVersion
3.0.0-beta.1
Reproduction link
https://github.com/nanomad/vue-cli-promise-test
Steps to reproduce
- Create a new project via vue-cli (accepts the defaults)
- Add the following to main.js
Promise.all([0]).then(function() {
alert("ALL OK");
})
- Run
yarn serve
- Open IE11
What is expected?
An alert with “ALL OK” appears
What is actually happening?
- No alert
- Error in console
Unhandled promise rejection TypeError: 0 is not iterable!
Seems like the babel preset for vue is pulling in the wrong polyfill
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
How to support promises in Internet Explorer 11?
IE11 neither supports arrow functions nor native Promises. Use a JS transpiler (like babel) or don't use ES6 features. For Promise support you ......
Read more >Troubleshooting Promise Polyfill Not Working as Expected
I had an interesting problem with Promise Polyfill to make promise and finally work on IE11. The page has multiple JS bundles.
Read more >promise-polyfill - npm
Lightweight ES6 Promise polyfill for the browser and node. Adheres closely to the spec. It is a perfect polyfill IE or any other...
Read more >Axios not working in IE11 even after using ES6-promise. #1694
Hey guys - so here is just a quick tip which could help some folks: Sometimes it can seem like the promise-polyfill is...
Read more >Promises is not supported in this environment. please polyfill ...
Hi, When the function modeler is called I'm getting the error (Promises is not supported in this environment. please polyfill promise) on IE...
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
Then you should probably report that in the Babel repo.
Filed a babel issue, seems like a feature detection error on IE10
https://github.com/babel/babel/issues/7395