3.1.0 breaks IE11
See original GitHub issueHi,
I’m using https://github.com/atlassian/react-beautiful-dnd which depends on this project. With the release of 3.1, this library appears to break IE11 with an error cannot redefine non-configurable property length
which I traced back to https://github.com/alexreardon/memoize-one/blob/master/src/index.js#L45 which was added in 3.1
If I forcefully revert to 3.0.1, IE11 works well again. Sorry I do not have a good test-case, so just heads up that there might be an issue with 3.1 which gets pulled into react-beautiful-dnd
by default now.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
3.1.0 breaks IE 11 · Issue #82 · blakeembrey/free-style - GitHub
The 3.1.0 update breaks IE 11 with: "Const must be initialized error" I think the main culprit is the use of const in...
Read more >Internet Explorer 11 desktop application ended support for ...
Internet Explorer mode in Microsoft Edge enables backward compatibility and will be supported through at least 2029. Additionally, Microsoft ...
Read more >Internet Explorer Still Does Not Go Away Today - Adrian Roselli
…Internet Explorer 11 desktop application will be retired and go out of support on June 15, 2022, for certain versions of Windows 10....
Read more >socket.io-client causing a syntax error on ie 11 - Next js
io-client uses debug dependency ~3.1.0 which won't break in IE 11. You can delete the socket.io-client folder in node_modules, then run npm i ......
Read more >blazor.polyfill - npm
Since Blazor 3.1.0-preview3.19555.2, including the polyfill on a Blazor WebAssembly project can cause some break, especially on Edge.
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
I have rolled back the .length and .name addition for now.
I have deprecated 3.1.0 and published 3.1.1 which does not modify the function properties. This gives us some breathing room to think about this a bit more and test approaches
@alexreardon That fix worked! Thank you for such a quick turnaround 😃