Sample
nanostores 1.5.0: Differentiate nanostores lifecycle pipeline abort semantics (onSet vs onNotify), reverse hook execution order with shared context, immediate synchronous effect lifecycle, batched macrotask timer vs synchronous computed, and mapCreator unmount cache eviction
Verified sample for npm nanostores 1.5.0: Differentiate nanostores lifecycle pipeline abort semantics (onSet vs onNotify), reverse hook execution order with…
sha256:494c8f810a863785af6c9eeb4597fcb99ff255b7e4485026bda45500600bb34d
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 many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
node linux x64 node node npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-16 |
| node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-18 |
Case
HOW- Goal
- Differentiate nanostores lifecycle pipeline abort semantics (onSet vs onNotify), reverse hook execution order with shared context, immediate synchronous effect lifecycle, batched macrotask timer vs synchronous computed, and mapCreator unmount cache eviction
- Packages
- Symbols
-
- nanostores.STORE_UNMOUNT_DELAY
- nanostores.allTasks
- nanostores.atom
- nanostores.batch
- nanostores.batched
- nanostores.cleanStores
- nanostores.computed
- nanostores.effect
- nanostores.map
- nanostores.mapCreator
- nanostores.onMount
- nanostores.onNotify
- nanostores.onSet
- nanostores.onStart
- nanostores.onStop
- nanostores.startTask
- nanostores.task
- Environment
- node
- Created
- 2026-08-16T06:22:09Z
Contract
- assert onSet passes a single object { abort, newValue, shared } (and { changed } for setKey) where calling event.abort() blocks the mutation before $store.value is modified
- assert onNotify aborts AFTER $store.value has already mutated, suppressing listener notifications while leaving the new value in the store
- assert lifecycle hooks execute in reverse registration order (reduceRight/LIFO) and share a mutable event.shared object across the event cycle
- assert .get() on an unmounted store triggers onStart and onStop synchronously while onMount remains active across the STORE_UNMOUNT_DELAY window
- assert effect() executes immediately and synchronously on creation with unwrapped store values, runs cleanup before each re-execution and unbind, and collapses updates inside batch()
- assert batched() defers notifications to a setTimeout macrotask while computed() notifies synchronously, but calling .get() on batched forces immediate recomputation and synchronous notification
- assert mapCreator caches stores by id, defers init() until onMount, and automatically evicts the cache entry when the store unmounts after STORE_UNMOUNT_DELAY
- assert task() and startTask() catch synchronous errors and async rejections, ensuring task counters decrement and allTasks() always resolves cleanly without hanging
- assert atom uses Object.is for change detection so +0 to -0 notifies while NaN to NaN does not, and that custom atom.eq and map.eqKey(oldVal, newVal, key) control notification behavior
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- src/stores.mjs
- test/contract.mjs