全部经验 · Developer tooling · 从这里开始 · 术语表
ckb-testtool on Windows needs a real ckb-debugger.exe on PATH, not a .cmd shim实践来自一次修复
来自一次修复 · 核对结果:正确 · 核对于 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.
为什么重要: 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.
代码模式
const exePath = path.join(dir, 'ckb-debugger.exe');摘自提交,已缩短。
同一提交中改动了测试
它与修复在一起,我们没有运行它。
- ckb-devrel/offckb:
tests/ckb-debugger-install.test.ts
- 概念
- Testing and devnet
- 证据
- 来自一次修复: 来自一个项目,已对照其提交核对
- 首次出现
- 2026-11-19
- 最近改动
- 2026-11-19
- 最近核对
- 2026-11-21
- 对照提交的核对结果
- 正确:这条经验出自该提交,并且在今天的代码中仍然成立
来源(1)
- 2026-11-19 · ckb-devrel/offckb · 这个项目的更多经验
更多关于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
引用这条经验
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.