I created this gist in order to help myself and others keep track of tips and tricks in order to make Gatsby v2 play nicely with Internet Explorer 10 and 11.
This is experience based. Please share your experiences when you have a solution to a problem.
If you suspect that an es6-based module is breaking your app, then try to add gatsby-plugin-compile-es6-packages and include the package as one of the modules.
| animated.DialogOverlay = animated(DialogOverlay) | |
| animated.DialogContent = animated(DialogContent) | |
| function NewPostDialog({ date, show, onDismiss }) { | |
| const rootRef = useRef(null) | |
| const transitions = useTransition(show, null, { | |
| from: { opacity: 0, y: -10, blur: 0 }, | |
| enter: { opacity: 1, y: 0, blur: 8 }, | |
| leave: { opacity: 0, y: -10, blur: 0 }, |
Hey everyone - this is not just a one off thing, there are likely to be many other modules in your dependency trees that are now a burden to their authors. I didn't create this code for altruistic motivations, I created it for fun. I was learning, and learning is fun. I gave it away because it was easy to do so, and because sharing helps learning too. I think most of the small modules on npm were created for reasons like this. However, that was a long time ago. I've since moved on from this module and moved on from that thing too and in the process of moving on from that as well. I've written way better modules than this, the internet just hasn't fully caught up.
@broros
otherwise why would he hand over a popular package to a stranger?
If it's not fun anymore, you get literally nothing from maintaining a popular package.
One time, I was working as a dishwasher in a restu
