From bc6ee2288ef7af7cf529ef3cd60d71d4c2aa32f1 Mon Sep 17 00:00:00 2001 From: thePR0M3TH3AN Date: Thu, 20 Aug 2026 09:05:13 -0400 Subject: [PATCH] Declare tsx where the fuzz runner actually lives MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The differential-fuzz CI job failed with "tsx: not found" — the TypeScript side of the fuzzer never ran at all, so the job was reporting on Python output alone. `tsx` was a devDependency of @seedpass/cli only, while the fuzz runner lives in packages/core and is invoked with cwd there. It worked locally because core's node_modules/.bin had a stale tsx from an earlier install, and could never work from a clean `pnpm install --frozen-lockfile`. Precisely the class of bug that only CI can see, on the first run after wiring these checks up. Declared in @seedpass/core rather than papering over it with a path or a --filter, so the invocation is correct by construction. Verified by removing core's node_modules, reinstalling frozen, and running CI's own seed 1 end to end: 1050 cases, no divergences. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01Vtx94nXDmNgXEeThUZP4QN --- js/packages/core/package.json | 1 + js/pnpm-lock.yaml | 3 +++ 2 files changed, 4 insertions(+) diff --git a/js/packages/core/package.json b/js/packages/core/package.json index a38a5f2d..6de6fcce 100644 --- a/js/packages/core/package.json +++ b/js/packages/core/package.json @@ -25,6 +25,7 @@ "@seedpass/test-vectors": "workspace:*", "@types/ws": "^8.18.1", "jsdom": "^30.0.1", + "tsx": "^4.20.0", "typescript": "^5.7.0", "vitest": "^3.0.0", "ws": "^8.21.3" diff --git a/js/pnpm-lock.yaml b/js/pnpm-lock.yaml index 7bb1a1c1..588830a4 100644 --- a/js/pnpm-lock.yaml +++ b/js/pnpm-lock.yaml @@ -68,6 +68,9 @@ importers: jsdom: specifier: ^30.0.1 version: 30.0.1(@noble/hashes@2.3.0) + tsx: + specifier: ^4.20.0 + version: 4.23.12 typescript: specifier: ^5.7.0 version: 5.9.3