xunnamius / babel-plugin-explicit-exports-references Goto Github PK

Aloha! Thank you for crafting this plugin. Extremely helpful. I was just curious if you had a particular license file in mind/plan to add to repo?

When transpiling to ES Modules (including setting "type": "module" in package.json) this breaks Jest tests with the error:

ReferenceError: module is not defined

It seems it doesn't take the targeted build type into account and just assumes it's building CommonJS modules. I know the options are limited and I'm not certain what the best solution is, but since ES Module adoption is only increasing it would be nice to have the option to not produce a broken build with Jest. Just wanted to at least raise the issue for consideration.

Errors look like:

ReferenceError: /repos/xscripts/src/assets/config/_conventional.config.js.ts: Container is falsy

This is probably due to the naive way new variables are created. Either way, this old project needs some of my attention!

Added the plugin to my Babel config. Works great running tests. However running with coverage (with default reporter) everything kind of blows up. Lots of reports of “Container” being falsy attributed to this plugin. Still trying to identify root cause.