CodeSampleX

Recordsnpmvite

Change the conditions
Fixed
Package version8.1.5 Package managernpm Execution contextnode
Filter OSalpine musl Runtimenode 22 Architecturex64 libcmusl Clear filters

Current conditions

vite @8.1.5alpine musl · 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
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-30

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 3

First observed break

5.4.21

executionContext=node

41 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

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.3.08.2.28.2.17.3.67.3.16.4.36.2.05.4.215.4.14
esbuild — — — 0.28.2 0.27.2 0.25.12 0.25.12 0.21.5 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 8.5.28
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 4.63.1
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.