Recordsnpmlightningcss
Change the conditions
Current conditions
lightningcss.transform @1.33.0musl · x64 · 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 (2)
- Project observations
- 0 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 2
- Last recorded
- 2026-08-18
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
windows 11 · x64 · node 24 · npm 11 · node
0 of 2 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.33.0
windows · node@24.13 · moduleSystem=esm · executionContext=node
3 FAIL · stage: PROJECT_PROCESS
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 | 1.33.0 | 1.32.0 |
|---|---|---|
| detect-libc | 2.1.2 | 2.1.2 |
Moved: 0 · unchanged at every release: 1
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.