CodeSampleX

Recordsnpmvite7.3.6vite.createServer

Change the conditions
Fixed
Symbolvite.createServer Architecturex64
Filter OSubuntu glibc Runtimenode 22 Package version7.3.6 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

vite.createServer @7.3.6ubuntu 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-29

Dependencies

LibraryVersionMeasured thereProjects
esbuild 0.28.2 contract passed 7 project-days
fdir 6.5.0 contract passed 7 project-days
picomatch 4.0.5 contract passed 2 project-days
picomatch 4.0.7 contract passed 5 project-days
postcss 8.5.26 contract passed 7 project-days
rollup 4.62.5 contract passed 3 project-days
rollup 4.63.0 contract passed 3 project-days
rollup 4.63.1 contract passed 1 project-day
tinyglobby 0.2.17 contract passed 6 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.

Library8.2.27.3.66.4.35.4.21
esbuild 0.28.2 0.25.12 0.21.5
picomatch 4.0.7 4.0.5 4.0.7
rollup 4.63.1 4.63.0 4.63.1
fdir 6.5.0 6.5.0
lightningcss 1.33.0
postcss 8.5.26 8.5.26 8.5.26 8.5.26
rolldown 1.2.6
tinyglobby 0.2.17 0.2.17 0.2.17

Moved: 3 · unchanged at every release: 5

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