| name | verify |
| description | Verify a Bun runtime change by driving the debug binary end-to-end. |
Verify a Bun runtime change
Build and drive the debug binary directly — never bun test, never import-and-call.
Build
bun bd --version
Drive
For any JS-visible change, run the debug binary with -e and observe stdout:
bun bd -e '<repro>'
For worker/subprocess-shaped changes, spawn a subprocess (still -e) so worker teardown / event-loop-idle paths are exercised. Cross-check against node -e '<same repro>' for Node-compat changes.
Gotchas
BUN_DEBUG_QUIET_LOGS=1 suppresses debug-build log spam.
- MessagePort's
.on/.off are added by requiring worker_threads — plain new MessageChannel() ports only have addEventListener until then.
- The debug+asan build is 10-100× slower than release; large-allocation stress tests can time out locally while passing in CI.