Recordsnpmvitefailure issue
Failure signature
UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×4
node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-09-04 · Last seen: 2026-09-05
sha256:986d98189e70…
vite.resolveConfig
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.
- 8.3.0 not measured
- 8.2.2 FAIL
- 8.2.1 not measured
- 8.2.0 not measured
- 7.3.6 not measured
- 7.3.1 not measured
- 6.4.3 FAIL
- 6.2.0 not measured
- 5.4.21 not measured
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×3 2026-09-05 → 2026-09-05
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-09-04 → 2026-09-04
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 | 8.3.0 | 8.2.2 | 8.2.1 | 7.3.6 | 7.3.1 | 6.4.3 | 6.2.0 | 5.4.21 |
|---|---|---|---|---|---|---|---|---|
| esbuild | — | — | — | 0.28.2 | 0.27.2 | 0.25.12 | 0.25.12 | 0.21.5 |
| picomatch | 4.0.7 | 4.0.7 | 4.0.5 | 4.0.5 | 4.0.3 | 4.0.5 | — | — |
| postcss | 8.5.28 | 8.5.28 | 8.5.26 | 8.5.26 | 8.5.6 | 8.5.26 | 8.5.28 | 8.5.25 |
| rolldown | 1.2.8 | 1.2.7 | 1.2.4 | — | — | — | — | — |
| rollup | — | — | — | 4.63.3 | 4.54.0 | 4.63.3 | 4.62.4 | 4.62.3 |
| tinyglobby | 0.2.17 | 0.2.17 | 0.2.17 | 0.2.17 | 0.2.15 | 0.2.17 | — | — |
| fdir | — | — | — | 6.5.0 | 6.5.0 | 6.5.0 | — | — |
| lightningcss | 1.33.0 | 1.33.0 | 1.33.0 | — | — | — | — | — |
| vitest | — | — | 4.1.10 | — | — | — | — | — |
Moved: 6 · 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: 7
- No failure domain was inferred for this failure.
Published answers for the affected releases
- vite 6.4.3: resolveConfig This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWvite.resolveConfignode 22.23.2 MIT-0 · 2026-09-05
- vite 6.4.3: defineConfig This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWvite.defineConfignode 22.23.2 MIT-0 · 2026-08-27
- vite 6.4.3 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWnode 22.23.2 MIT-0 · 2026-08-23