Module parse error after upgrading from cheerio v1.0.0-rc.12 to v1.0.0 in Nuxt (Webpack 4) environment

[FireOnIcecube]

Description

After upgrading cheerio from v1.0.0-rc.12 to v1.0.0, I started seeing module parse errors in my Nuxt project. Reverting back to v1.0.0-rc.12 fixes the issue, so it seems specific to v1.0.0.

Error Logs

ERROR in /home/cooperwang/projects/web-project/node_modules/.pnpm/node_modules/encoding-sniffer/dist/commonjs/index.js Module not found: Error: Can't resolve 'node:stream' in '/home/cooperwang/projects/web-project/node_modules/.pnpm/node_modules/encoding-sniffer/dist/commonjs'

ERROR in /home/cooperwang/projects/web-project/node_modules/.pnpm/node_modules/parse5-parser-stream/dist/index.js Module not found: Error: Can't resolve 'node:stream' in '/home/cooperwang/projects/web-project/node_modules/.pnpm/node_modules/parse5-parser-stream/dist'

ERROR in ./node_modules/cheerio/dist/esm/index.js Module not found: Error: Can't resolve 'node:stream' in '/home/cooperwang/projects/web-project/sites/w12/node_modules/cheerio/dist/esm'

ERROR in /home/cooperwang/projects/web-project/node_modules/.pnpm/node_modules/undici/index.js 123:39 Module parse failed: Unexpected token (123:39) 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

Steps to Reproduce

1. Install or upgrade to cheerio@1.0.0 in a Nuxt 2 project using Webpack 4.
2. Run pnpm run dev or pnpm run build.
3. Observe the module parse errors above.

Expected Behavior

The build should succeed without errors, as it does when using cheerio@1.0.0-rc.12.

Environment

• Operating System: Linux
• Node Version: v20.12.2
• Nuxt Version: 2.17.4
• CLI Version: 3.22.5
• Nitro Version: -
• Package Manager: pnpm@9.14.4
• Builder: webpack 4.47.0
• User Config: -
• Runtime Modules: -
• Build Modules: -

Additional Context

• The error only appears after upgrading to cheerio@1.0.0.
• Downgrading to cheerio@1.0.0-rc.12 resolves the issue.

Any guidance or workaround would be greatly appreciated. Thank you!

[Chinoman10]

Running an Astro website here, using Bun as the package manager/runtime, etc., and there's apparently an issue with cheerio 1.0.0 and htmlparser2 and the node 'entities' (I never even heard of this before).
Maybe this helps:

Since I'm using Bun, a solution I'm trying is doing a local patch of cheerio's htmlparser2, changing import { fromCodePoint } from "entities/lib/decode.js"; to import { fromCodePoint } from "entities"; (and had to do the same thing for Tokenizer.js).

Hope this helps the devs patch it; I don't even know if this is a cheerio problem or an htmlparser2's problem 🤷

[Chinoman10]

Seems there's an issue opened on htmlparser2: fb55/htmlparser2#1782