Recordsnpmelectron-vite5.0.0electron-vite.bytecodePlugin
Change the conditions
Current conditions
electron-vite.bytecodePlugin @5.0.0debian glibc · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
5.0.0
windows · node@24.13 · moduleSystem=cjs · executionContext=node
3 FAIL
· stage: UNKNOWN
· fingerprint: sha256:3e5f03903e292d9b19daef82b234201615ab763216b97feec6f325b598b3380d
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/core | 7.29.7 | PASS All observations passed | contract passed | 15 project-days |
| @babel/plugin-transform-arrow-functions | 7.29.7 | PASS All observations passed | contract passed | 15 project-days |
| cac | 6.7.14 | PASS All observations passed | contract passed | 15 project-days |
| esbuild | 0.25.12 | PASS All observations passed | contract passed | 15 project-days |
| magic-string | 0.30.21 | PASS All observations passed | contract passed | 14 project-days |
| picocolors | 1.1.1 | PASS All observations passed | contract passed | 14 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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.
Recent failure clusters
-
observed UNKNOWN exit 1 ERROR Evidence gap ×1 5.0.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:1f882fb2e944…✘ [ERROR] Could not resolve <str> · failed to load config from <path> · <path>:<n> · let error = new Error(text);node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 5.0.0 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:ac1a96fa941c…Contract test failed: AssertionError [ERR_ASSERTION]: out/preload/index.js must be created by build · at run (<url>) { · generatedMessage: false, …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06Diagnostic re-verification candidate