Recordsnpmbrowserslist4.28.2
Change the conditions
Current conditions
browserslist @4.28.2windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-13
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.28.8
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
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 | 4.29.5 | 4.29.0 | 4.28.9 | 4.28.8 | 4.28.7 | 4.28.1 |
|---|---|---|---|---|---|---|
| baseline-browser-mapping | 2.11.36 | 2.11.28 | 2.11.23 | 2.11.15 | 2.11.19 | 2.9.11 |
| caniuse-lite | 1.0.30001826 | 1.0.30001815 | 1.0.30001810 | 1.0.30001809 | 1.0.30001806 | 1.0.30001761 |
| electron-to-chromium | 1.5.482 | 1.5.452 | 1.5.427 | 1.5.414 | 1.5.415 | 1.5.267 |
| node-releases | 2.0.63 | 2.0.58 | 2.0.55 | 2.0.53 | 2.0.53 | 2.0.27 |
| update-browserslist-db | 1.3.4 | 1.3.4 | 1.2.3 | 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.