Recordsnpmupdate-browserslist-db1.3.4
Change the conditions
Current conditions
update-browserslist-db @1.3.4debian glibc · x64 · node 22 · npm · node
package-level total, not an API
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 4 / 4
- Contract verifications
- 1 / 1
- Usage records
- 7
- Independent reporting peers
- 1
- Last recorded
- 2026-11-11
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.3.4
linux · node@22.23 · moduleSystem=esm · executionContext=node
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:513a2c6f086d838409c2a19c7758b8a0cd8a53d40349da643c48314fda25c6ae
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| escalade | 3.2.0 | PASS All observations passed | contract passed | 25 project-days |
| picocolors | 1.1.1 | PASS All observations passed | contract passed | 25 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.
| Library | 1.3.4 | 1.3.3 | 1.3.2 | 1.3.1 | 1.3.0 | 1.2.3 |
|---|---|---|---|---|---|---|
| escalade | 3.2.0 | 3.2.0 | 3.2.0 | 3.2.0 | 3.2.0 | 3.2.0 |
| picocolors | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 | 1.1.1 |
Moved: 0 · unchanged at every release: 2
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
-
observed UNKNOWN exit 1 Evidence gap ×1 1.3.4 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:513a2c6f086d…<url> · const resolved = getTargets( · ^ · TypeError: getTargets is not a functionnpm · unclassified-diagnostic · outer npm test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-08 · Last seen: 2026-11-08Diagnostic re-verification candidate
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×1 1.3.4 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:2c4eb57fcc76…AssertionError [ERR_ASSERTION]: Missing expected exception. · at <url> · at ModuleJob.run (node:internal/modules/esm/module_job:<n>:<n>) …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-12 · Last seen: 2026-11-12