wrong setting about parse-domain HOT 7 CLOSED

why not just push cjs and esm at same time?

from parse-domain.

Yes, since 6.0.0 the package is published as ECMAScript module only. Your options are:

• migrate your code to ECMAScript modules. It's the best long term solution but probably a lot of work. If you don't migrate, you will see this kind of error with every dependency update since more and more packages are migrating to ESM
• import it asynchronously via await import("parse-domain") (see https://nodejs.org/dist/latest-v16.x/docs/api/modules.html)
• stay on version 5.0.0

from parse-domain.

Is this why I am getting the following?
Error [ERR_REQUIRE_ESM]

from parse-domain.

Is this why I am getting the following?
Error [ERR_REQUIRE_ESM]

yes

from parse-domain.

It appears this is intentional so this issue will probably be closed

BREAKING CHANGE: parse-domain will now be released as native ECMAScript module. There's no CommonJS build anymore. If you're still using CommonJS, you need to import it asynchronously using await import("parse-domain"). If you're still using Node 12, you may need to update it to the latest 12.x version.

42f54e8

from parse-domain.

We already did it for two years, but cross-publishing ESM and CJS is not as easy as it sounds. There are a couple of pitfalls I don't want to care of any longer. A lot of module maintainers are slowly switching to ESM, so you probably won't have a choice in the long term.
If you're still using CJS, you can use version 5.0.0. It already has the parse-domain-update command, so you can keep the internal list up-to-date.

from parse-domain.

@bluelovers Maybe that's an option for you: #142 (comment)

from parse-domain.