CodeSampleX

Compatibilitynpm@babel/helper-module-imports8.0.0@babel/helper-module-imports.addSideEffect

Change the conditions
Fixed
Symbol@babel/helper-module-imports.addSideEffect libcglibc
Filter OSubuntu glibc Runtimenode 22 Package version8.0.0 Architecturex64 Package managernpm 10 Execution contextnode Clear filters

Current conditions

@babel/helper-module-imports.addSideEffect @8.0.0ubuntu glibc · x64 · node 22 · npm 10 · node

0 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 failed (1)

Project observations
1 / 1
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-08-30

Dependencies

LibraryVersionMeasured thereProjects
@babel/traverse 8.0.4 contract passed 5 project-days
@babel/types 8.0.4 contract passed 5 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.

Library8.0.07.29.7
@babel/traverse 8.0.4 7.29.7
@babel/types 8.0.4 7.29.7

Moved: 2 · unchanged at every release: 0

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.

Recent failure clusters