since facing "ENOENT: no such file or directory, open 'node:stream'" issue

[nehaAgarwalext]

Hi! 👋

Firstly, thanks for your work on this project! 🙂

Today I used patch-package to patch [email protected] for the project I'm working on.

Here is the diff that solved my problem:

diff --git a/node_modules/parse5-parser-stream/dist/cjs/index.js b/node_modules/parse5-parser-stream/dist/cjs/index.js
index a5002be..4e9a5fd 100644
--- a/node_modules/parse5-parser-stream/dist/cjs/index.js
+++ b/node_modules/parse5-parser-stream/dist/cjs/index.js
@@ -1,7 +1,7 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ParserStream = void 0;
-const node_stream_1 = require("node:stream");
+const { Readable } = require('stream');
 const parse5_1 = require("parse5");
 /* eslint-disable unicorn/consistent-function-scoping -- The rule seems to be broken here. */
 /**

This issue body was partially generated by patch-package.

[chinna2580]

I am also facing the same issue with my next app, how can i resolve this issue? @nehaAgarwalext @inikulin

Unable to patch the package

[soswow]

Same here. Seems like cheerio got released from RC to final version 1.0.0 which is a dependency of enzyme (at least as of version 3.11.0 (which many of us has) and after some yarn.lock updating now I get the same thing. So random.

[soswow]

My solution was to define forced resolution:

"resolutions": {
    "cheerio@npm:^1.0.0-rc.3": "1.0.0-rc.12"
  },

which fixed the problem for now

[43081j]

can someone please provide a reproduction?

the suggested patch isn't going to fly and doesn't tell us much. some way of recreating the error would be incredibly helpful

[wooorm]

My guess is that people are on old webpack. I don’t know from the top of my head but I think it’s webpack 4 or such that doesn’t support node: prefixes.

@soswow What are you using? Enzyme hasn’t been published in 5 years apparently. Are you on very old things?