From f36f119ef0f0633f5d86d5fb51846b002296be20 Mon Sep 17 00:00:00 2001 From: Remco Haszing Date: Thu, 26 Mar 2026 18:48:00 +0100 Subject: [PATCH] Loosen the version of @types/node MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `@types/node` is a bit different from other type definitions. Most type definitions from DefinitelyTyped define module type mirroring the public package structure. If two versions are installed, they both define types for a different version of the package. `@types/node` however, declares modules other than `node`. These module definitions may clash. Also `unified-engine` doesn’t have a dependency on Node.js 22, it has a dependency on Node.js builtins that are available between Node.js 16 and the current latest version. Packages solve this by specifying the `@types/node` dependency range as `*`. The only one that stands out in many cases is `unified-engine`. --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 205d972..c829d4d 100644 --- a/package.json +++ b/package.json @@ -9,7 +9,7 @@ "@types/concat-stream": "^2.0.0", "@types/debug": "^4.0.0", "@types/is-empty": "^1.0.0", - "@types/node": "^22.0.0", + "@types/node": "*", "@types/unist": "^3.0.0", "concat-stream": "^2.0.0", "debug": "^4.0.0",