CodeSampleX

Recordsnpm@vitejs/plugin-react

Change the conditions
Fixed
Package version5.2.0 Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

@vitejs/plugin-react @5.2.0ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 9 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (4)

Project observations
35 / 35
Contract verifications
0 / 9
Usage records
1
Independent reporting peers
2
Last recorded
2026-09-04
Evidence you can open

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 2 · Steady 4

First observed break

5.2.0

windows · node@24.13 · moduleSystem=cjs · executionContext=node

3 FAIL · stage: UNKNOWN · fingerprint: sha256:3e5f03903e292d9b19daef82b234201615ab763216b97feec6f325b598b3380d

View exact conditions View failure cluster
Library Version Health Measured there Projects
@rolldown/pluginutils 1.0.0-rc.3 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
react-refresh 0.18.0 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
@babel/core 7.29.7 PASS All observations passed contract passed 11 project-days
@babel/plugin-transform-react-jsx-self 7.29.7 PASS All observations passed contract passed 11 project-days
@babel/plugin-transform-react-jsx-source 7.29.7 PASS All observations passed contract passed 11 project-days
@types/babel__core 7.20.5 PASS All observations passed contract passed 11 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.

Library5.2.04.7.0
@rolldown/pluginutils 1.0.0-rc.3 1.0.0-beta.27
react-refresh 0.18.0 0.17.0
@babel/core 7.29.7 7.29.7
@babel/plugin-transform-react-jsx-self 7.29.7 7.29.7
@babel/plugin-transform-react-jsx-source 7.29.7 7.29.7
@types/babel__core 7.20.5 7.20.5

Moved: 2 · unchanged at every release: 4

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.