Open oliviertassinari opened 3 years ago
ie 11 was released at 2013, I remember that year I worked as an electrician inside deep Russia. Then few years after I became a web developer (just more money nothing else). Since that time I changed few places, got additional child, and IE 11 is still here :-) even I think it was dead few years ago ;-) We will take a look, just for fun, wtf is happening :-)
If you exclude node_modules
from being processed by your bundling tool (e.g. Webpack) making an exception for rifm
might help. It worked for us 🙂
Would bump for this. Since mui v5 is only out recently, any projects still relying in mui v4 and using the date picker library encounter an IE11 crash due to inclusion of this library. Naturally I'd prefer that the picker library update to IE11 support and drop the use of rifm, as they should for mui4 compliance, but as they have closed the project I don't see that happening, so instead I've come to the "source" of the issue for help 😛
I have found that this dependency breaks support for projects relying on IE 11 investigating https://github.com/mui-org/material-ui/issues/24167. For instance, see the arrow function returned in http://unpkg.com/rifm.