-
Just a heads-up: apparently [Gnome 45 will require extensions to be ESModules](https://news.itsfoss.com/gnome-45-extensions/).
-
When chained after `css-loader` 6.x with [`options.esModule: true`](https://github.com/webpack-contrib/css-loader#esmodule) (the default), and [`options.modules.namedExport: true`](https://github.com/…
-
## 🐛 Bug Report
I'm working in an ES2017 codebase compiled with TypeScript, Babel, and webpack. It seems that in certain contexts, using the default import of FBT fails because `babel-plugin-fbt` s…
-
Hello,
Thank you for your project.
I've found that when using `browsersWithSupportForFeatures` I get an error when using esmodules, but not when using commonjs. I've attached 2 test files below.…
-
**Is your feature request related to a problem? Please describe.**
One possible issue that we have encountered while using the `aws-otel-nodejs` lambda layer is the incompatibility with Middy, a midd…
-
### Describe the Bug
While using https://github.com/artberri/rollup-plugin-istanbul in an `extension.config.js` file, if a file of the extension contains `process.env.NODE_ENV`, the build breaks du…
-
Not sure how it could happen but it appears to be babel/esmodules related. The error is `Unexpected token export` on `dist/popper-utils.js:1002` :-(
-
I'm using esmodules with moduleResolution set to NodeNext. This means relative import paths require explicit file extensions. Is there a way to configure this requirement out of the box?
-
Hello, I have a problem. The problem should come from my configuration. But I need help.
I used ts-jest、babel-jest and @vue/vue3-jest ，But when I run the jest, I got an error
Vitejs doesn't support require statement which is used …