Sample

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

sha256:494c8f810a863785af6c9eeb4597fcb99ff255b7e4485026bda45500600bb34d

PUBLISHED L3_CONTRACT_PASS MIT-0

Case

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 HOW
Packages: nanostores 1.5.0
Environment: node
Created: 2026-08-16T06:22:09Z

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

node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9