After the release of `v1.0.0-rc.11`, `Module parse failed: Unexpected token` occurs

[ygnoh]

As the title says, since v1.0.0-rc.11 the below error occurs:

START:
ℹ ｢wdm｣: Compiled successfully.
ℹ ｢wdm｣: Compiling...
✖ ｢wdm｣: 
ERROR in ./node_modules/htmlparser2/lib/esm/index.js 59:9
Module parse failed: Unexpected token (59:9)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     return getFeed(parseDOM(feed, options));
| }
> export * as DomUtils from "domutils";
| // Old name for DomHandler
| export { DomHandler as DefaultHandler };
 @ ./node_modules/cheerio/lib/esm/index.js 11:0-68
 @ ./node_modules/enzyme/build/ReactWrapper.js
 @ ./node_modules/enzyme/build/index.js
 @ ./test.entry.js

I think it's a bug of cheerio, because it has been occurring since 3 days ago when the v1.0.0-rc.11 released.

Could you please look into this bug?

[krislavten]

I have the same issue.

[fb55]

The bundler is choking on export * as DomUtils from "domutils";. It seems like Webpack has supported the export * as ... syntax since ~2020 (see webpack/webpack@3cf8299), and an update should fix things. Alternatively, you could also force the bundler to pick up the CommonJS code that's still shipped with Cheerio.

For umijs/umi#8109: umijs seems to have switch to rollup afaict (at least I haven't been able to find a Webpack version), so there is a chance that updating some internal packages might do the trick?

Please let me know if this makes sense!

[nicolashu]

same issue

[mike-lischke]

People might not be able to upgrade a library, if that's actually brought in by other modules (e.g. via create-react-app). Changes that require upgrades of other libraries should always be accompanied by at least a minor version increase.

Locking package import to cheerio@1.0.0-rc.10 fixed the issue for me. But that should really not be needed! Please do such changes in another release that raise at least the minor version number, so they are not automatically picked up.

[ygnoh]

@mike-lischke Do you know a way to lock the package version on lerna?

In my project, enzyme is using cheerio. I couldn't find a way to lock the subdependecy of enzyme.
I tried npm-force-resolutions and overrides. But unfortunately lenra does not support them :(

[ygnoh]

I resolved this problem by declaring cheerio in devDependencies like:

  "devDependencies": {
    "cheerio": "=1.0.0-rc.3",
    ...

Hope this helps.

[bindoon]

I have the same issue. help me.

[gladson1976]

I've tried the suggestion by @ygnoh, and it works fine in my local build.. but fails in the GitLab pipeline..
anyone have any ideas ?

[yanglbme]

lock the version in dependencies, like this doocs/md@551b07d

[bindoon]

it seems enzyme is using cherrio, how could I lock cherrio in enzyme