Repository navigation
Commit 84c4cd2
committed
compile: make the source-map fixture read the version band it runs in
`--enable-source-maps` is withheld on Node 26.0.0-26.7.x, because enabling it
there turns a no-message `assert.ok(false)` into a TypeError (nodejs/node#63169,
fixed by 26.8.1). The fixture asserted a mapped frame unconditionally, so on any
Node in that band it reported FAIL for an augmentation nub deliberately declines
to make - including on the harness's own default of 26.5.0.
It now reads the support state off the process, so the row goes vacuous exactly
where nub declines to remap. The same branch makes the plain-Node column differ
where the flag IS injected: type-stripping preserves line numbers, so plain Node
named `app.ts` by itself and the row proved nothing on the versions nub augments.
Verified across the boundary with a compiled artifact per band - 24.20.0 and
26.8.1 resolve to `app.ts` in both the reference and the artifact while plain
Node does not, and 26.7.0 reports no support in all three columns. A control
built with no map still fails the row on both safe bands.1 parent bcbe419 commit 84c4cd2
1 file changed
Lines changed: 16 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
10 | 24 | | |
11 | 25 | | |
12 | 26 | | |
| |||
18 | 32 | | |
19 | 33 | | |
20 | 34 | | |
21 | | - | |
| 35 | + | |
| 36 | + | |
22 | 37 | | |
0 commit comments