Story
Workspace package imports remain readable while Bun tests run beside other repository checks, so a portable package-boundary test does not fail on a dependency tree that is otherwise valid.
What failed
While reviewing PR #764 at the tree later committed as 25d1597981b7da3b06511f4e13865142d5688d92, the terminal package boundary suite ran under Bun 1.4.0 while Deno checks were also reading the prepared worktree:
/private/tmp/xmd755-bun140.11dchm/bun-darwin-aarch64/bun test packages/terminal/tests/package-boundary.test.ts
TG21f: runtime and core export none of the terminal domain failed while dynamically importing the workspace runtime package:
EISDIR reading ".../node_modules/@executablemd/runtime"
The failure is at import("@executablemd/runtime"), not in the suite's source-tree walker. It therefore means Bun observed the installed workspace package entry as a directory it could not resolve, even though the prepared workspace normally resolves that package.
This was a local feedback run, so there is no CI run URL.
Evidence of intermittence
The identical command on the identical tree passed immediately when run alone:
No source, manifest, lockfile, or dependency setup changed between the failure and the passing rerun. The #764 repair changes neither Bun's resolver nor shared-state mutation; its root manifest additions declare two missing test dependencies and the standalone Bun 1.4.0 run confirms those resolve.
The overlap is a condition, not yet an established cause. It may expose a transient workspace-link state or a Bun resolver defect; the current evidence does not distinguish them.
Acceptance
- The same Bun package import remains readable while the repository's supported concurrent checks run against one prepared worktree.
- A regression reproduces the overlapping condition without relying on an elapsed-time window.
- The cause is identified and fixed without weakening the terminal package-boundary assertions.
- A green rerun alone does not close this issue.
Story
Workspace package imports remain readable while Bun tests run beside other repository checks, so a portable package-boundary test does not fail on a dependency tree that is otherwise valid.
What failed
While reviewing PR #764 at the tree later committed as
25d1597981b7da3b06511f4e13865142d5688d92, the terminal package boundary suite ran under Bun 1.4.0 while Deno checks were also reading the prepared worktree:/private/tmp/xmd755-bun140.11dchm/bun-darwin-aarch64/bun test packages/terminal/tests/package-boundary.test.tsTG21f: runtime and core export none of the terminal domainfailed while dynamically importing the workspace runtime package:The failure is at
import("@executablemd/runtime"), not in the suite's source-tree walker. It therefore means Bun observed the installed workspace package entry as a directory it could not resolve, even though the prepared workspace normally resolves that package.This was a local feedback run, so there is no CI run URL.
Evidence of intermittence
The identical command on the identical tree passed immediately when run alone:
No source, manifest, lockfile, or dependency setup changed between the failure and the passing rerun. The #764 repair changes neither Bun's resolver nor shared-state mutation; its root manifest additions declare two missing test dependencies and the standalone Bun 1.4.0 run confirms those resolve.
The overlap is a condition, not yet an established cause. It may expose a transient workspace-link state or a Bun resolver defect; the current evidence does not distinguish them.
Acceptance