Records/npm/browserslist/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 4.29.0 PASS 1 passing observations
• 4.28.9 PASS 11 passing observations
• 4.28.8 FAIL
• 4.28.7 FAIL
• 4.28.2 not measured
• 4.28.1 PASS 1 passing observations

Where it reproduced

• executionContext=node · moduleSystem=esm · os=windows · runtime=node@22.16 ×3 2026-08-23 → 2026-08-23
• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-08-26 → 2026-08-26
• executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-25 → 2026-08-25

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release 4.28.1 → first failing release 4.28.7

  Releases between them never measured at this stage: 1

  What differs across the boundary

  • baseline-browser-mapping 2.9.11 → 2.11.19, 2.11.24, 2.11.7 hypothesis
  • caniuse-lite 1.0.30001761 → 1.0.30001806, 1.0.30001810 hypothesis
  • electron-to-chromium 1.5.267 → 1.5.398, 1.5.415, 1.5.430 hypothesis
  • node-releases 2.0.27 → 2.0.51, 2.0.53, 2.0.55 hypothesis
  • update-browserslist-db 1.2.3 → 1.2.3, 1.3.1, 1.3.3 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last failing release 4.28.8 → first passing release 4.28.9

  What differs across the boundary

  • baseline-browser-mapping 2.11.21, 2.11.23 → 2.11.15, 2.11.16, 2.11.18, 2.11.19, 2.11.20, 2.11.21 hypothesis
  • caniuse-lite 1.0.30001810 → 1.0.30001809, 1.0.30001810 hypothesis
  • electron-to-chromium 1.5.422, 1.5.427 → 1.5.411, 1.5.412, 1.5.414, 1.5.415, 1.5.416, 1.5.418, 1.5.419, 1.5.420, 1.5.421, 1.5.422 hypothesis
  • node-releases 2.0.54, 2.0.55 → 2.0.53, 2.0.54 hypothesis
  • update-browserslist-db 1.2.3, 1.3.2, 1.3.3 → 1.3.0, 1.3.1, 1.3.2 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

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.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• Releases in this window never measured at PROJECT_TEST: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• browserslist 4.28.8: Parse multi-environment configuration sections, load environment configurations, and query Node.js versions with browserslist Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbrowserslist.findConfigbrowserslist.loadConfigbrowserslist.nodeVersionsbrowserslist.parseConfignode 22.23.2 MIT-0 · 2026-08-24
• browserslist 4.28.8: Evaluate custom usage statistics with browserslist popularity queries and coverage calculations Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbrowserslistbrowserslist.coveragenode MIT-0 · 2026-08-17
• browserslist 4.28.8: Demonstrate that @babel/preset-env retains in-memory browserslist configuration caches across transforms, requiring explicit browserslist.clearCaches() when on-disk target files change. Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW@babel/preset-envtransformSyncbrowserslist.clearCachesnode MIT-0 · 2026-08-16
• browserslist 4.28.7: parseConfig Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbrowserslist.parseConfignode 22.23.2 MIT-0 · 2026-09-17
• browserslist 4.28.7: loadConfig Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbrowserslist.loadConfignode 22.23.2 MIT-0 · 2026-09-17
• browserslist 4.28.7: findConfigFile Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbrowserslist.findConfigFilenode 22.23.2 MIT-0 · 2026-09-17