From fe6f9614cc4137e672637a01cf687f53b3f4911e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcos=20P=C3=A9rez=20Ferro?= Date: Sun, 27 Sep 2026 19:28:03 +0200 Subject: [PATCH] fix(deps): approve @parcel/watcher build script pnpm refuses the entire install with ERR_PNPM_IGNORED_BUILDS because @parcel/watcher (a transitive dependency of jest-haste-map, used only for fast filesystem watching in Jest's --watch mode) isn't in allowBuilds. CI doesn't use --watch mode, so the native binding is never exercised, but pnpm still blocks the whole install until every build script is explicitly reviewed. @parcel/watcher is the official MIT-licensed package from the Parcel bundler project; its install script just builds/fetches its native binding, same pattern as unrs-resolver/esbuild already allowed here. Verified with a clean install + the full CI suite (format, lint, typecheck, 268 tests) on the jest-bump branch this was blocking. --- pnpm-workspace.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml index 9a8c8b3..006aa96 100644 --- a/pnpm-workspace.yaml +++ b/pnpm-workspace.yaml @@ -12,8 +12,14 @@ # binary. Same reasoning as unrs-resolver: the binary comes from a prebuilt # optional dependency that esbuild resolves at runtime, so the check is not # needed for it to work — `likec4 validate` exercises exactly that path. +# @parcel/watcher (transitive, via jest-haste-map) is a native filesystem +# watcher used only by Jest's --watch mode, which CI doesn't use; its install +# script builds/fetches its native binding from source, the same pattern as +# fsevents or esbuild. Official MIT-licensed package from the Parcel bundler +# project - allowed to build so plain `pnpm install` stops failing. allowBuilds: '@nestjs/core': false + '@parcel/watcher': true '@scarf/scarf': false esbuild: false unrs-resolver: false