Recordsnpm@babel/helper-create-regexp-features-plugin
Change the conditions
Current conditions
@babel/helper-create-regexp-features-plugin @7.29.7alpine musl · x64 · node 22 · npm · node
1 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 came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-04
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
createRegExpFeaturePlugin
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
7.29.7
linux · node@22.23 · moduleSystem=cjs · executionContext=node
4 FAIL
· stage: UNKNOWN
· fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2
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 | 8.0.1 | 7.29.7 |
|---|---|---|
| @babel/helper-annotate-as-pure | 8.0.0 | 7.29.7 |
| semver | 7.8.5 | 6.3.1 |
| regexpu-core | 6.4.0 | 6.4.0 |
Moved: 2 · unchanged at every release: 1
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.