Repository navigation
Commit 137f3b3
committed
🚨 Classify the Q7 distribution harness as Deno's own (#934)
Discovery finds every `scripts/tests/*.test.ts` and hands it to all three
runtimes unless the manifest says otherwise, so the new packaging harness was
being scheduled under Node and Bun — where `Deno.execPath()`, the canonical
host compile and the dnt closure build have no meaning. Classifying it is the
act that file was missing.
Nothing it proves is dropped. The Node and Bun consumers are the ones this
harness launches: source Node through the repository's `tsx` loader, source
Bun, and the packed closure under both. Excluding the driver from those
runtimes leaves every one of those launches exactly where it was, and what the
engine does inside a document stays proven on every runtime by
`query-component.test.ts`.
One entry, in the list the adjacent Deno build and npm tooling already use,
under the issue the manifest keeps that decision in. Discovery, the runners,
the harness, its assertions and `exclusions.deno` are untouched.1 parent b9a49ba commit 137f3b3
1 file changed
Lines changed: 6 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
71 | 71 | | |
72 | 72 | | |
73 | 73 | | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
74 | 80 | | |
75 | 81 | | |
76 | 82 | | |
| |||
0 commit comments