ESM + Relative imports without .js extension causes "ReferenceError: require is not defined in ES module scope"

[ctian1]

If you have a package that uses ESM + relative imports without .js extension, ex:

export * from './utils'

ncc will think that it can't find utils and produce eval("require")("./utils"), resulting in "ReferenceError: require is not defined in ES module scope".

[styfle]

Does it work when running your source file with node directly?

Typically you need either { "type": "module" } in package.json or rename the file to .mjs

https://nodejs.org/api/esm.html#enabling

[styfle]

• See also: "require is not defined in ES module scope" and mixed require/import using ESM with native modules #791

[marcofranssen]

I'm facing the same with typescript.

See here for the failure: marcofranssen/setup-kubectl#114

For some strange reason it does still work with ncc 0.36.0.

On another project https://github.com/marcofranssen/setup-kubectl it works flawless. I have been comparing both my projects like crazy, I can't find the reason why it isn't working in one of the projects.

Tried with and without type: "module" in package.json.