Sample
Distinguish pre-completion refCount reset from post-completion replay caching with RxJS 7.8.2 shareReplay
sha256:d112f3535ec9d167ce90038085b8d434e0fe16e5f972f073b2bd564ae094f541
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Distinguish pre-completion refCount reset from post-completion replay caching with RxJS 7.8.2 shareReplay HOW
- Packages
- rxjs 7.8.2
- Environment
- node
- Created
- 2026-08-17T02:02:27Z
Contract
- assert shareReplay with bufferSize one immediately replays the latest value to a concurrent subscriber without starting a second source subscription
- assert refCount keeps the source alive until the last subscriber unsubscribes and then tears it down
- assert dropping to zero subscribers before source completion clears the replay buffer so the next subscriber starts a fresh source without receiving the stale value
- assert after source completion the final value and completion remain cached for a late subscriber without another source subscription or teardown
Files
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9