CodeSampleX

Recordsnpmbrowserslist4.29.5

Change the conditions
Fixed
Package version4.29.5 Package managernpm Execution contextnode
Filter OSdebian glibc Runtimenode 22 Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

browserslist @4.29.5debian glibc · x64 · node 22 · npm · 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
5
Independent reporting peers
1
Last recorded
2026-11-12

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 9 · Steady 0

First observed break

4.29.5

linux · node@22.23 · moduleSystem=esm · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:513a2c6f086d838409c2a19c7758b8a0cd8a53d40349da643c48314fda25c6ae

Library Version Health Measured there Projects
baseline-browser-mapping 2.11.35 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
baseline-browser-mapping 2.11.36 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
caniuse-lite 1.0.30001823 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
caniuse-lite 1.0.30001826 CANDIDATE Correlated change; unproven combination builds observed 4 project-days
electron-to-chromium 1.5.478 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
electron-to-chromium 1.5.481 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
electron-to-chromium 1.5.482 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
node-releases 2.0.63 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
update-browserslist-db 1.3.4 CANDIDATE Correlated change; unproven combination contract passed 23 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.

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