Recordsnpmbabel-plugin-istanbul6.1.1
Change the conditions
Current conditions
babel-plugin-istanbul @6.1.1windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
1 of 1 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-17
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @babel/helper-plugin-utils | 7.29.7 | contract passed | 6 project-days |
| @istanbuljs/load-nyc-config | 1.1.0 | contract passed | 6 project-days |
| @istanbuljs/schema | 0.1.6 | contract passed | 6 project-days |
| istanbul-lib-instrument | 5.2.1 | contract passed | 6 project-days |
| test-exclude | 6.0.0 | contract passed | 6 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 | 7.0.1 | 6.1.1 |
|---|---|---|
| istanbul-lib-instrument | 6.0.3 | 5.2.1 |
| @babel/helper-plugin-utils | 7.29.7 | 7.29.7 |
| @istanbuljs/load-nyc-config | 1.1.0 | 1.1.0 |
| @istanbuljs/schema | 0.1.6 | 0.1.6 |
| test-exclude | 6.0.0 | 6.0.0 |
Moved: 1 · unchanged at every release: 4
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.