node-fetch unusable with esm package

Given an index.js file with import fetch from "node-fetch" When I run cli command node -r esm index.js Then I should see the script import fetch and run.

Version 3 gives this error.
 at Object.Module._extensions..js (internal/modules/cjs/loader.js:1080:13) {
 code: 'ERR_REQUIRE_ESM'
}

Now, I’ve read the similar threads on this. One thing that hasn’t been mentioned, that the maintainers overlook, is there are still MAJOR projects out there that can’t be used with ESM directly. Cucumber.js is one of them. The top level project must be CJS for cucumber to work, but you can convince it to work seemlessly with the ESM package.

[tenbits]

This is extremely opinioned position, which shouldn’t be the case for the lib, as both should be supported, while they are and will be both first-class module systems. A consumer should be able to use the library disregarding of which module system he/she uses. This is even disrespectful to those, who for any of the reasons use cjs.

[jimmywarting]

we also have similar cjs/esm issues open that are basically a dupl of this, so closing this one… There isn’t any issue with node-fetch itself This (now) ESM-only package works as intended. if you have a problem with using ESM-only packages or any other solution highlighted in #1227 then it’s really up to you to fix it

There is also a discussion about having a exposed cjs file that only export fetch (not headers, Response and Request) that is related to this: #1327