-
Notifications
You must be signed in to change notification settings - Fork 26k
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
IE11 errors on main.js because of const
in for (const ...
#4334
Comments
@tashburn Try with next@6.0.1. It should be fine. |
Going to close based on @oliviertassinari's comment. It'd be tremendously helpful if you provide full steps to reproduce when creating issues, otherwise it takes more time than it should to check out particular issues. Thanks 🙏 |
@tashburn Hi, I have same problem with external dependency. Did you solved this? |
@omeraplak I solved it by replacing
|
@tashburn |
@omeraplak |
Hey, I am getting the same issue with
Is there a known fix for this issue? |
@kedarguy @tashburn This my setup; .babelrc
pages/_document.js
next.config.js
npm i --save @babel/polyfill |
@omeraplak Thank you for your answer. Where does |
@rap2hpoutre hi, I was updated |
Expected Behavior
Next deployments should work in IE11.
Current Behavior
My Next deployment does not work in IE11.
The error is
I looked at that place in
main.js
, which has this snippet--I looked online, and apparently IE11 doesn't allow
const
orlet
infor
loops, likefor (const var ...
.I removed all these
for (const
andfor (let
forms from my code and redeployed, but got the same result. I believe it's because there are 9 modules in mynode_modules
that use thefor (const ...
form. I can't replace these modules.Is there some way to have next build the code and convert these
for (const
andfor (let
forms tofor (var
orfor (...
so I can support IE11?I am using Typescript, but I don't think that should make a difference.
Steps to Reproduce (for bugs)
Deploy any code with a
for (const
loop in it.Your Environment
The text was updated successfully, but these errors were encountered: