Babel-node not working with "type": "module" in package.json

I have the following script that I’m running with npx babel-node script.js

let a = 0;
let b = 1;
console.log(a ?? b);

It executes fine with my babel config

{
	"plugins": ["@babel/plugin-proposal-nullish-coalescing-operator"]
}

When I add “type”: “module” to my package.json file, the npx babel-node script.js command fails to run and I get the error SyntaxError: Unexpected token '?'.

So it seems specifying my package as module, prevents babel-node from loading the babel config?

[bradley]

So what is the suggestion here? My understanding is that we use @babel/node for developing a node backend with babel configuration, and then we are supposed to compile the backend using the babel cli for production. In order to keep using import in my node app, I use "type": "module" for the compiling step… which breaks @bable/node and therefore development… this seems like an issue to me, shouldn’t this be reopened?

[nicolo-ribaudo]

https://github.com/nicolo-ribaudo/babel-native-esm-demo

my eslint config, my rollup config

I don’t know if those tools support native ESM configs, but Babel does.