Records npm eslintfailure issue

Failure signature

UNKNOWN exit 1 ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL Evidence gap ×4

> devhotel-workspace@0.4.3 typecheck <path> · > pnpm -r typecheck · Scope: 4 of 5 workspace projects · packages/shared typecheck$ tsc --noEmit

Evidence quality: complete · pnpm · unclassified-diagnostic · outer pnpm · gap stage-unknown · First recorded: 2026-09-01 · Last seen: 2026-09-01

sha256:3b99548df64e…

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.

10.9.0 not measured
10.8.1 not measured
10.8.0 not measured
9.39.5 FAIL
9.39.4 not measured
9.20.0 not measured
8.57.1 not measured

Where it reproduced

executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×4 2026-09-01 → 2026-09-01

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	10.9.0	9.39.5	9.20.0	8.57.1
@eslint-community/eslint-utils	4.10.1	4.10.1	4.10.1	4.9.0
@eslint/config-array	0.23.5	0.21.2	0.19.2	—
@eslint/config-helpers	0.7.0	0.4.2	—	—
@eslint/core	1.2.1	0.17.0	0.11.0	—
@eslint/eslintrc	—	3.3.7	3.3.6	2.1.4
@eslint/js	—	9.39.5	9.20.0	8.57.1
@eslint/plugin-kit	0.7.2	0.4.1	0.2.8	—
ajv	6.15.0	6.15.0	6.15.0	6.12.6
eslint-scope	9.1.2	8.4.0	8.4.0	7.2.2
eslint-visitor-keys	5.0.1	4.2.1	4.2.1	3.4.3
espree	11.2.0	10.4.0	10.4.0	9.6.1
esquery	1.7.0	1.7.0	1.7.0	1.6.0
file-entry-cache	—	8.0.0	8.0.0	6.0.1
minimatch	—	3.1.5	3.1.5	3.1.2
@eslint-community/regexpp	4.12.2	4.12.2	4.12.2	4.12.2
@humanfs/node	0.16.8	0.16.8	0.16.8	—
@humanwhocodes/config-array	—	—	—	0.13.0
@humanwhocodes/module-importer	1.0.1	1.0.1	1.0.1	1.0.1
@humanwhocodes/retry	0.4.3	0.4.3	0.4.3	—
@nodelib/fs.walk	—	—	—	1.2.8
@types/estree	1.0.9	1.0.9	1.0.9	—
@types/json-schema	—	—	7.0.15	—
@ungap/structured-clone	—	—	—	1.3.0
chalk	—	4.1.2	4.1.2	4.1.2
cross-spawn	7.0.6	7.0.6	7.0.6	7.0.6
debug	4.4.3	4.4.3	4.4.3	4.4.3
doctrine	—	—	—	3.0.0
escape-string-regexp	4.0.0	4.0.0	4.0.0	4.0.0
esutils	2.0.3	2.0.3	2.0.3	2.0.3
fast-deep-equal	—	3.1.3	3.1.3	3.1.3
find-up	—	5.0.0	5.0.0	5.0.0
glob-parent	—	6.0.2	6.0.2	6.0.2
globals	—	—	—	13.24.0
graphemer	—	—	—	1.4.0
ignore	—	5.3.2	5.3.2	5.3.2
imurmurhash	—	0.1.4	—	0.1.4
is-glob	—	4.0.3	—	4.0.3
is-path-inside	—	—	—	3.0.3
js-yaml	—	—	—	4.1.1
json-stable-stringify-without-jsonify	—	1.0.1	—	1.0.1

Moved: 14 · unchanged at every release: 32 Longer lists are cut here; the counts above cover all of them.

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: 6
No failure domain was inferred for this failure.

Published answers for the affected releases

eslint 9.39.5 HOW MIT-0 · 2026-08-26

Back to the package

Records/npm/eslint/failure issue