CodeSampleX

Recordsnpmbrowserslist4.28.1

Change the conditions
Fixed
Package version4.28.1
Filter OSwindows 11 Runtimenode 24 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

browserslist @4.28.1windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

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

Project observations
19 / 66
Contract verifications
0 / 9
Usage records
45
Independent reporting peers
1
Last recorded
2026-09-01

Dependencies

LibraryVersionMeasured thereProjects
baseline-browser-mapping 2.9.11 contract passed 1 project-day
caniuse-lite 1.0.30001761 contract passed 1 project-day
electron-to-chromium 1.5.267 contract passed 1 project-day
node-releases 2.0.27 contract passed 1 project-day
update-browserslist-db 1.2.3 contract passed 1 project-day

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.

Library4.28.84.28.74.28.1
baseline-browser-mapping 2.11.15 2.11.7 2.9.11
caniuse-lite 1.0.30001809 1.0.30001810 1.0.30001761
electron-to-chromium 1.5.414 1.5.415 1.5.267
node-releases 2.0.54 2.0.53 2.0.27
update-browserslist-db 1.3.0 1.3.1 1.2.3

Moved: 5 · unchanged at every release: 0

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 27 recorded failure clusters. The rest are single reports.