CodeSampleX

Recordsnpmwrangler4.133.0

Change the conditions
Fixed
Runtimenode 24 Package version4.133.0
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

wrangler @4.133.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 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 failed (1)

Project observations
nothing at this coordinate
Contract verifications
0 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 8

First observed break

4.133.0

windows · node@24.13 · moduleSystem=esm · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:61ae78379d96c7fcad024ae19f04b55daa60405f8347cf58c6df9be1daea8c2c

View exact conditions View failure cluster
Library Version Health Measured there Projects
@cloudflare/kv-asset-handler 0.5.0 PASS All observations passed contract passed 1 project-day
@cloudflare/unenv-preset 2.16.1 PASS All observations passed contract passed 1 project-day
blake3-wasm 2.1.5 PASS All observations passed contract passed 1 project-day
esbuild 0.28.1 PASS All observations passed contract passed 2 project-days
miniflare 5.20260916.0-alpha PASS All observations passed contract passed 2 project-days
path-to-regexp 6.3.0 PASS All observations passed contract passed 1 project-day
unenv 2.0.0-rc.24 PASS All observations passed contract passed 2 project-days
workerd 1.20260916.1 PASS All observations passed contract passed 2 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.

Recent failure clusters