Recordsnpmelectron-vitefailure issue
Failure signature
PROJECT_TEST Evidence gap ×5
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-21 · Last seen: 2026-08-25
electron-vite.defineConfig electron-vite.externalizeDepsPlugin
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST 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=esm · os=windows · runtime=node@22.16 ×3 2026-08-23 → 2026-08-23
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-25 → 2026-08-25
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release 3.1.0 → first passing release 5.0.0
Both trees resolved every dependency to the same version. Nothing here moved.
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 | 5.0.0 | 3.1.0 |
|---|---|---|
| @babel/core | 7.29.7 | 7.29.7 |
| @babel/plugin-transform-arrow-functions | 7.29.7 | 7.29.7 |
| cac | 6.7.14 | 6.7.14 |
| esbuild | 0.25.12 | 0.25.12 |
| magic-string | 0.30.21 | 0.30.21 |
| picocolors | 1.1.1 | 1.1.1 |
Moved: 0 · unchanged at every release: 6
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.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- electron-vite 3.1.0: loadConfigFromFile 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. HOWelectron-vite.loadConfigFromFile MIT-0 · 2026-09-17
- electron-vite 3.1.0: externalizeDepsPlugin 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. HOWelectron-vite.externalizeDepsPluginnode 22.23.2 MIT-0 · 2026-08-26
- electron-vite 3.1.0: 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. HOWelectron-vite.defineConfig MIT-0 · 2026-08-26