Recordsnpmchokidar4.0.3
Change the conditions
Current conditions
chokidar @4.0.3ubuntu glibc · x64 · node 22 · npm 10 · 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
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.0.3
windows · node@24.13 · moduleSystem=cjs · executionContext=node
8 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| readdirp | 4.1.2 | CANDIDATE Correlated change; unproven combination | contract passed | 4 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 | 4.0.3 | 3.6.0 |
|---|---|---|
| readdirp | 4.1.2 | 3.6.0 |
| anymatch | — | 3.1.3 |
| braces | — | 3.0.3 |
| glob-parent | — | 5.1.2 |
| is-binary-path | — | 2.1.0 |
| is-glob | — | 4.0.3 |
| normalize-path | — | 3.0.0 |
Moved: 1 · unchanged at every release: 6
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.