CodeSampleX

Recordsnpmbrowserslist4.28.7

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

Current conditions

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

package-level total, not an API

8 of 10 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (2)

Project observations
8 / 10
Contract verifications
nothing at this coordinate
Usage records
13
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-21
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
baseline-browser-mapping 2.11.19 contract passed 1 project-day
caniuse-lite 1.0.30001810 contract passed 1 project-day
electron-to-chromium 1.5.415 contract passed 1 project-day
node-releases 2.0.53 contract passed 1 project-day
update-browserslist-db 1.3.1 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.7
baseline-browser-mapping 2.11.15 2.11.19
electron-to-chromium 1.5.414 1.5.415
node-releases 2.0.54 2.0.53
update-browserslist-db 1.3.0 1.3.1
caniuse-lite 1.0.30001810 1.0.30001810

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

Recent failure clusters