All lessons · Developer tooling · Start here · Glossary
ckb-testtool on Windows needs a real ckb-debugger.exe on PATH, not a .cmd shimWorkingFrom one fix
From one fix · Check: right · Checked 2026-11-21
ckb-testtool spawns `ckb-debugger` through Node child_process without a shell, and on Windows that resolves a bare name only to an .exe on PATH, never to a .cmd file (and spawning .cmd shell-less is refused since Node 18.20.2 / 20.12.2). A ckb-debugger.cmd wrapper alone makes native mock tests fail with "ckb-debugger not found", so place an actual ckb-debugger.exe (a hard link or copy of the binary) in a PATH directory.
Why it matters: With only a ckb-debugger.cmd shim on PATH, ckb-testtool's shell-less spawn cannot find the debugger on Windows. Native mock tests then fail with "ckb-debugger not found" even though the debugger is installed.
Pattern
const exePath = path.join(dir, 'ckb-debugger.exe');Taken from the commit, shortened.
A test changed in the same commit
It sits next to the fix. We did not run it.
- ckb-devrel/offckb:
tests/ckb-debugger-install.test.ts
- Concepts
- Testing and devnet
- Evidence
- From one fix: from one project, checked against its commit
- First seen
- 2026-11-19
- Last changed
- 2026-11-19
- Last checked
- 2026-11-21
- Check against the commit
- right: the lesson follows from its commit and still holds in the code today
Sources (1)
- 2026-11-19 · ckb-devrel/offckb · more from this project
More about Developer tooling
- ckb-vm-js 0.2.0 (npm) checks header hash instead of rejecting the field
- Derive devnet Spore and system script cell deps from a fresh OffCKB export
- Pass wasm bytes to ckb-vm-js createVerifier in Node
Do you maintain a project this lesson came from? Confirm or correct it
Cite this lesson
LusoCryptoLabs, "ckb-testtool on Windows needs a real ckb-debugger.exe on PATH, not a .cmd shim", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/ckb-testtool-on-windows-needs-a-real-ckb-debugger-exe-on-pat, CC BY 4.0, last changed 2026-11-19.