Compatibilitynpmelectron-vite5.0.0electron-vite.build
Change the conditions
Current conditions
electron-vite.build @5.0.0ubuntu glibc · x64 · node 22 · npm 10 · node
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-31
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @babel/core | 7.29.7 | contract passed | 2 project-days |
| @babel/plugin-transform-arrow-functions | 7.29.7 | contract passed | 2 project-days |
| cac | 6.7.14 | contract passed | 2 project-days |
| esbuild | 0.25.12 | contract passed | 2 project-days |
| magic-string | 0.30.21 | contract passed | 1 project-day |
| picocolors | 1.1.1 | contract passed | 1 project-day |
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.