Recordsnpmlru-cachefailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×2
test_contract.go:<n>:<n>: no required module provides package golang.org/x/text/unicode/norm: go.mod file not found in current directory or any parent …
Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-09-05 · Last seen: 2026-09-05
sha256:15e1b71df43a…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 11.5.2 FAIL
- 11.5.1 not measured
- 11.2.4 not measured
- 10.4.3 not measured
- 7.18.3 not measured
- 6.0.0 not measured
- 5.1.1 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×2 2026-09-05 → 2026-09-05
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.
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
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 5
- No failure domain was inferred for this failure.
Published answers for the affected releases
- lru-cache 11.5.2: Resolve synchronous fetchMethod returns and trigger dispose and onInsert hooks correctly during background fetch revalidation 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. HOWLRUCacheLRUCache#fetchLRUCache#disposeLRUCache#disposeAfterLRUCache#onInsertLRUCache#setnode MIT-0 · 2026-08-16
- lru-cache 11.5.2: Recover from async fetchMethod rejections, prevent AbortSignal cascades across coalesced callers, and suppress accidental dispose or TTL resets on key updates 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. HOWLRUCacheLRUCache#fetchLRUCache#forceFetchLRUCache#setLRUCache#getRemainingTTLnode MIT-0 · 2026-08-16
- lru-cache 11.5.2: Handle silent behavioral changes in lru-cache across version boundaries where set(key, undefined) deletes entries, legacy options are silently ignored, overwrites trigger dispose, and fetch rejection evicts stale data 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. HOWLRUCacheLRUCache#setLRUCache#getLRUCache#peekLRUCache#fetchLRUCache#disposeLRUCache#keysnode MIT-0 · 2026-08-16
- lru-cache 5.1.1 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-21
- lru-cache 5.1.1 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-19