reactivando / use-pubsub-js / 28133808053

100%

master: 80%

push

github

feat: react19/useSubscribe built on useEffectEvent (opt-in subpath) (#87)

* feat: add react19/useSubscribe built on useEffectEvent (opt-in subpath)

For React 19.2+, an optional useSubscribe that reads the latest handler through
useEffectEvent instead of the handlerRef pattern — closing the small window
where a publish delivered between a handler prop change and the ref-update effect
could invoke the previous handler under concurrent rendering. Same public API.

- New `use-pubsub-js/react19/useSubscribe` subpath (+ typesVersions). The default
  entry is unchanged and stays React 18+ compatible (no useEffectEvent import).
- Tests mirror the default hook (receive, latest-handler-without-resubscribe,
  unmount, unsubscribe/resubscribe, token change, isUnsubscribe). The suite is
  skipped on React < 19.2 (via React.version) so the React-18 CI cell stays green.
- CI: coverage is gated on the React 19 cell only, since the react19 suite is
  intentionally skipped on 18.

125 tests, 100% coverage (on React 19), lint clean, attw + publint green for the
new subpath, e2e 10/10.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix(react19): clear error on React <19.2 (CJS); clarify ci + test comments

Adversarial review follow-ups:
- Add a runtime guard so React <19.2 CJS callers get a clear "requires React
  19.2+" error instead of an obscure "useEffectEvent is not a function" (v8-ignored
  — unreachable on the React-19 test platform). Note: ESM consumers on <19.2 fail
  earlier at the named import, which is the documented constraint.
- Comment why the GH Actions `&& '--coverage' || ''` idiom is safe here.
- Clarify that the "latest handler" test asserts external parity (the concurrent
  window useEffectEvent closes isn't reproducible in jsdom).

Not added: e2e import smoke for the subpath — it requires React >=19.2 in the e2e
sandbox (which resolves 19.1.1), and subpath resolution is already covered by
attw + publint. Pre-unmount delive... (continued)

31 of 31 branches covered (100.0%)

Branch coverage included in aggregate %.

20 of 20 new or added lines in 1 file covered. (100.0%)

211 of 211 relevant lines covered (100.0%)

36.1 hits per line