-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arrow functions in webpackBootstrap with browserslist: "IE >= 11" #11753
Comments
…use IE >= 10 for now due to (webpack/webpack#11753)
Fix #11754 |
When is this fix going to be published? Is it going to be part of 5.1.4? |
@evilebottnawi can we re-open this? I am running into the same problem on |
@sethomas double check your webpack version, I can't reopen issue without reproducible steps, sorry |
@evilebottnawi Odd, I'll chalk it up to me having to deal with IE 11 that threw me off, all is well, sorry for wrong information and thanks for the response. |
@sethomas setting |
I'm still running into this problem, but only with our production build in a docker image. My local development build works fine. My webpack version is 5.21.2 |
Also happens with the latest webpack version (5.24.2) but at least the workaround suggested by @amok fixes it for me |
With OpenLayers there were also arrow functions in the generated code. webpack version 5.30.0 Using @amok's suggestion fixed the transpilation of arrow functions. Hope this information will help you to reproduce, @alexander-akait. |
Bug report
What is the current behavior?
With
browserslist: "IE >= 11"
in my package.json there are arrow functions in generated webpackBootstrap code. It works correctly if I use IE >= 10 in my package.json.If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
I would expect the generated code to not have arrow functions for IE >= 11 since IE11 does not support arrow functions.
Other relevant information:
webpack version: 5.1.3
Node.js version: v14.6.0
Operating System: Ubuntu 20.04 LTS (WSL2)
Additional tools:
The text was updated successfully, but these errors were encountered: