Recordsnpmdmg-builderfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
> wslpad@1.0.2 lint · > eslint . · <path> · 77:<n> error Unexpected control character(s) in regular expression: \x1b no-control-regex
Evidence quality: complete · npm · unclassified-diagnostic · outer npm run · gap stage-unknown · First recorded: 2026-09-15 · Last seen: 2026-09-15
sha256:6cf9c24b033d…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-09-15 → 2026-09-15
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 26.15.3 | 25.1.8 |
|---|---|---|
| app-builder-lib | 26.15.3 | 25.1.8 |
| builder-util | 26.15.3 | 25.1.7 |
| js-yaml | 4.3.2 | 4.3.0 |
| builder-util-runtime | — | 9.2.10 |
| fs-extra | 10.1.0 | 10.1.0 |
| iconv-lite | — | 0.6.3 |
Moved: 3 · unchanged at every release: 3
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.