From 2058558753ac3a1e64e1e16aca8bb822d94a5d95 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E7=A7=A6=E5=A5=87?= Date: Mon, 11 May 2026 09:51:06 +0800 Subject: [PATCH] chore(deps): document @types/node 20.x pin in overrides The override pinning @types/node to 20.19.1 (while engines require Node >=22) is intentional: bumping to @types/node@22.x re-introduces a Dirent type regression that breaks @qwen-code/qwen-code-core/sessionService tests. Add a sibling "//@types/node" note inside `overrides` so future maintainers see the rationale and know when to revisit the pin without having to dig through PR #3860 history. Generated with AI Co-authored-by: Qwen-Coder --- package.json | 1 + 1 file changed, 1 insertion(+) diff --git a/package.json b/package.json index abf295213..7aaf5eedb 100644 --- a/package.json +++ b/package.json @@ -78,6 +78,7 @@ }, "baseline-browser-mapping": "^2.9.19", "normalize-package-data": "^7.0.1", + "//@types/node": "Pinned to 20.x even though engines require Node >=22. Upgrading to @types/node@22.x re-introduces a Dirent type regression in @qwen-code/qwen-code-core/sessionService tests. Revisit once the upstream type for Dirent stabilises (see PR #3860 discussion).", "@types/node": "20.19.1", "react": "19.2.4", "react-dom": "19.2.4"