Recordsnpmwhich-typed-array1.1.20
Change the conditions
Current conditions
which-typed-array @1.1.20windows 11 · x64 · node 24 · npm 11 · 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-08-13
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.1.19
windows · node@24.13 · executionContext=node · moduleSystem=cjs
4 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2
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.1.22 | 1.1.19 |
|---|---|---|
| call-bind | 1.0.9 | 1.0.8 |
| available-typed-arrays | 1.0.7 | 1.0.7 |
| call-bound | 1.0.4 | 1.0.4 |
| for-each | 0.3.5 | 0.3.5 |
| get-proto | 1.0.1 | 1.0.1 |
| gopd | 1.2.0 | 1.2.0 |
| has-tostringtag | 1.0.2 | 1.0.2 |
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.