Recordsnpmfind-upfailure issue
Failure signature
UNKNOWN exit 1 ERR_PACKAGE_PATH_NOT_EXPORTED Evidence gap ×1
node:internal/modules/esm/resolve:<n> · return new ERR_PACKAGE_PATH_NOT_EXPORTED( · ^ …
Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:b9a7518ba7bb…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×1 2026-09-01 → 2026-09-01
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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 | 5.0.0 | 4.1.0 | 2.1.0 |
|---|---|---|---|
| locate-path | 6.0.0 | 5.0.0 | 2.0.0 |
| path-exists | 4.0.0 | 4.0.0 | — |
Moved: 1 · 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.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- find-up 4.1.0: sync 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. HOWfind-up.syncnode 22.23.2 MIT-0 · 2026-08-30
- find-up 4.1.0: find files and directories up the directory tree with find-up 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. HOWfindUpfindUp.existsfindUp.stopfindUp.syncfindUp.sync.existsnode 22.23.2 MIT-0 · 2026-08-26