CodeVetter · Repo Unpack · Testing signals
ReactiveX/rxjs
Tests and CI were inspected, not executed; no passing result is asserted by this report. Evidence spans Vitest source tests, classified ported suites, Node package/tooling checks, browser contracts, and pinned WPT. The inspected coverage is bounded, and the legacy site's tests and native-mode fallback behavior require separate interpretation.
- Source tests use Vitest; inspected extension-kernel tests assert assignment descriptors, non-global public Symbols, preserved platform methods, and absence of RxJS string additions.
- The fast-check lifecycle property generates subscribe/abort/next/complete/error actions and checks fanout, activation/teardown accounting, and cleanup; RXJS_FUZZ_RUNS defaults to 200.
- @rxjs/test fixtures distinguish independent cold timelines, shared platform timelines, absolute hot timelines, construction policy, and virtualized timers/clocks.
- Migration file tests cover exact planned output, omitted lifecycle refusal, lexical traversal, escaping symlinks, duplicate canonical paths, and batch preflight behavior.
- Ported Vitest runs select cold or platform suites and disable file parallelism; native mode without a global Observable selects native-unavailable.spec.ts rather than exercising native behavior.
- Main CI runs package gates on Node 22.13.0 and 24, makes Node 26 advisory, and separately checks exact cold/polyfill audit baselines.
- Observable WPT pins revision 6a009d73f0d315941b90cac13a9523a2a08c631b and Chrome 150; CI verifies imports and runs lifecycle/kernel/conformance checks, with latest Chrome scheduled as advisory.
- Release readiness defines browser, Webpack, performance, packed adoption, Deno/Bun, and desktop/iOS Safari gates; the documentation app separately configures Jasmine/Karma with Chrome.