CodeSampleX

Recordsnpmpostcss8.5.26Container#insertBefore

Change the conditions
Fixed
SymbolContainer#insertBefore Architecturex64
Filter OSalpine musl Runtimenode 22 Package version8.5.26 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

Container#insertBefore @8.5.26alpine 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
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-27

Dependencies

LibraryVersionMeasured thereProjects
nanoid 3.3.18 contract passed 14 project-days
picocolors 1.1.1 contract passed 14 project-days
source-map-js 1.2.1 contract passed 14 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.5.268.5.25
nanoid 3.3.18 3.3.18
picocolors 1.1.1 1.1.1
source-map-js 1.2.1 1.2.1

Moved: 0 · 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.

Recent failure clusters

Showing the 12 most-reported of 15 recorded failure clusters. The rest are single reports.