CodeSampleX

Recordsnpm@electron/universal2.0.1makeUniversalApp

Change the conditions
Fixed
OSdebian glibc SymbolmakeUniversalApp
Filter Runtimenode 22 Package version2.0.1 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

makeUniversalApp @2.0.1debian glibc · x64 · node 22 · npm · node

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 (2)

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 7

First observed break

2.0.1

windows · executionContext=node

5 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
@electron/asar 3.4.1 PASS All observations passed contract passed 20 project-days
@malept/cross-spawn-promise 2.0.0 PASS All observations passed contract passed 20 project-days
debug 4.4.3 PASS All observations passed contract passed 20 project-days
dir-compare 4.2.0 PASS All observations passed contract passed 19 project-days
fs-extra 11.4.0 PASS All observations passed contract passed 19 project-days
minimatch 9.0.9 PASS All observations passed contract passed 18 project-days
plist 3.1.1 PASS All observations passed contract passed 19 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.

Library2.0.32.0.1
@electron/asar 3.4.1 3.4.1
@malept/cross-spawn-promise 2.0.0 2.0.0
debug 4.4.3 4.4.3
dir-compare 4.2.0 4.2.0
fs-extra 11.4.0 11.4.0
minimatch 9.0.9 9.0.9
plist 3.1.1 3.1.1

Moved: 0 · unchanged at every release: 7

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