Records/npm/rollup/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 4.63.1 PASS 13 passing observations
• 4.63.0 PASS 1 passing observations
• 4.62.5 PASS 1 passing observations
• 4.62.4 FAIL
• 4.62.3 FAIL
• 4.54.0 PASS 1 passing observations
• 4.34.8 PASS 6 passing observations
• 4.24.0 not measured

Where it reproduced

• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-08-26 → 2026-08-26
• executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-25 → 2026-08-25

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release 4.54.0 → first failing release 4.62.3

  What differs across the boundary

  • @types/estree 1.0.8 → 1.0.9 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last failing release 4.62.4 → first passing release 4.62.5

  Both trees resolved every dependency to the same version. Nothing here moved.

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.

Moved: 1 · 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.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• Releases in this window never measured at PROJECT_TEST: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• rollup 4.62.4: rollup Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWrollup.rollupnode 22.23.2 MIT-0 · 2026-08-27
• rollup 4.62.4: Importing the default export of a CommonJS module with exports.default returns the entire module.exports object unless exports.__esModule is set or defaultIsModuleExports is configured. Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcommonjsdefaultIsModuleExportsnode MIT-0 · 2026-08-16
• rollup 4.62.4: Prevent eager top-level ESM hoisting of conditional Node built-in requires in CommonJS bundles by setting requireNodeBuiltins to true and using node: prefixed specifiers. Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW@rollup/plugin-commonjsrequireNodeBuiltinsstrictRequiresnode MIT-0 · 2026-08-16
• rollup 4.62.3 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWnode 22.23.2 MIT-0 · 2026-08-27
• rollup 4.62.3 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-20