resolveConfig doesn't work in IE11 and Edge #1241
Replies: 6 comments
-
@gilesbutler I ran into this as well, resolved by updating my webpack rule for js files to include the
Then I had to configure Babel to transform modules. Using CJS, but UMD worked as well. Ideally I want to use ESM, but that caused other errors. |
Beta Was this translation helpful? Give feedback.
-
Hey @garand, thanks for following up and nice find. I'm not working on that project anymore so I can't test unfortunately. If I need to use Thanks |
Beta Was this translation helpful? Give feedback.
-
Hey @garand , could you share how you've configured Babel to transform modules? I'm having the same issue in Nuxt. Thanks. |
Beta Was this translation helpful? Give feedback.
-
@schellenbergk Does that above snippet not work for you? https://babeljs.io/docs/en/babel-preset-env#modules I set the |
Beta Was this translation helpful? Give feedback.
-
Thanks @garand , I ended up using a different package which solved the issue already. |
Beta Was this translation helpful? Give feedback.
-
I've run into this issue when using For anyone using Next.js, next-transpile-modules plugin works great to transpile this down to ES5. const withTranspiledModules = require('next-transpile-modules')(['tailwindcss'])
module.exports = withTranspiledModules({
// your next.config.js
}) |
Beta Was this translation helpful? Give feedback.
-
I've just come across this on two sites I've been working on. Using the following code...
Causes the following error in IE11 and Edge...
Beta Was this translation helpful? Give feedback.
All reactions