fix(package): Allow imports of cheerio/lib/utils

[blixt]

As used by Enzyme here (and which broke after upgrading Cheerio):

https://github.com/enzymejs/enzyme/blob/master/packages/enzyme/src/Utils.js#L11

Fixes #2600

[fb55]

Thanks @blixt!

[ljharb]

@fb55 this still doesn't solve the issue, because of #2601 (comment)

[fb55]

@ljharb I'm not sure I follow. How can an import not be either an import or a require? Are there platforms that use export maps for other module systems (UMD etc.)?

[ljharb]

@fb55 because there are versions of node - that enzyzme supports - that don't support conditions at all, or that only support the default condition.

[fb55]

Please correct me if I'm wrong: Doesn't this only affect Node versions that support ESM behind an --experimental-modules flag? As (1) nobody should use an experimental flag in production, and (2) there is full support in non-breaking updates, I don't think it is worth to keep supporting this.

[ljharb]

No, it does not. It affects node 13.0-13.6, with no flags passed.

[ljharb]

To be clear, you're arguing against adding a few bytes to package.json, versus some packages simply not being able to use cheerio at all without a semver-major change.

[fb55]

It affects node 13.0-13.6, with no flags passed.

Interesting! Thanks for the context.

you're arguing against adding a few bytes to package.json

My bigger picture is that I updated Cheerio's dependencies (and their dependencies) to be ESM as well, while never supplying a default field. If I wanted to add support for this, it would involve updating ~15 modules. And that's quite a bit of mundane work that I'm not certain is needed — so far, nobody has asked for this to be supported. Hope that makes sense!

[ljharb]

That is fair, but there was also no need to update anything to ESM :-/ so it's unfortunate that unnecessary work is prompting more work to be done.