Recordsnpmbrowserslist4.28.7browserslist.parseConfig
Change the conditions
Current conditions
browserslist.parseConfig @4.28.7ubuntu glibc · x64 · node 22 · npm 10 · node
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| 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.
| Library | 4.28.8 | 4.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.