Syntax error in ie11 with nextjs
See original GitHub issueSyntax error in ie11
-> class Dom7 ....
Issue Analytics
- State:
- Created 4 years ago
- Reactions:10
- Comments:22
Top Results From Across the Web
SCRIPT1002: Syntax error in Next JS website in IE11 ...
If we try to see the problematic line of code then we can notice that it contains => Arrow functions . Arrow functions...
Read more >IE11 & Next.js 12 version have syntax error with rewrites in ...
What example does this report relate to? with rewrites in next.config.js What version of Next.js are you using?
Read more >Supported Browsers and Features - Next.js
If your own code or any external npm dependencies require features not supported by your target browsers (such as IE 11), you need...
Read more >Any good guides on getting my app to run well in IE11? - Reddit
You open your app in IE11. Open the console. Check exactly where it broke. It (most likely) says „Syntax error“ or something is...
Read more >Create React App IE11 : SCRIPT1002: Syntax Error How to ...
Create React App IE11 : SCRIPT1002: Syntax Error How to get rid of it. You've been living in a happy Disney land of...
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
So, you wouldn’t believe it but the “Swiper” library author @nolimits4web silently deleted my bug report from his repository: https://github.com/nolimits4web/swiper/issues/3047 Very childish, rude and unprofessional. I guess I’ll have to look for better alternatives to the “Swiper” library.
In the meantime, for everyone having their Internet Explorer broken by the “Swiper” library here’s the workaround I found that stops the “Swiper” library from breaking Internet Explorer:
webpack.config.js
).babel-loader
there.exclude
from/node_modules/
(the default on the internet) to/node_modules[\/\\](?!(swiper|dom7)[\/\\])/
(I saw the idea in react-id-swiper’spackage.json
).dom7
andswiper
packages (doing the work thedom7
/swiper
library author should have done before releasing those untranspiled).Internet Explorer is still a popular browser in some areas. Breaking it is unacceptable.
@mathishuettl FWIW I added a custom alias for swiper, something like this:
Not ideal, not the best but does the trick.