Compatibilitynpmbabel-plugin-istanbul
Change the conditions
Current conditions
babel-plugin-istanbul @6.1.1ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 5 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
- 15 / 15
- Contract verifications
- 0 / 5
- Usage records
- 1
- Independent reporting peers
- 2
- Last recorded
- 2026-08-31
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 5 passed
Verified — this network ran a contract at this coordinate.
-
babel-plugin-istanbul.default
0 of 2 passed
Verified — this network ran a contract at this coordinate.
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.