Records npm@vitejs/plugin-react

Change the conditions

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.

0 of 9 passed

Open the next level

Verified — this network ran a contract at this coordinate.
@vitejs/plugin-react.preambleCode

3 of 3 passed

Open the next level

Observed — real project builds reported from this coordinate.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 4

First observed break

4.7.0

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

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster

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.2.0	4.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.