reactivando / use-pubsub-js / 28106619323

100%

master: 80%

push

github

fix(usePublish): guard initial publish under StrictMode + harden debounceMs (#65)

- #1 StrictMode double-fire: add a useRef guard so the isInitialPublish
  mount effect fires exactly once even when React StrictMode double-
  invokes effects in dev. No change to normal/production behavior (the
  empty-dep effect already fires once; a genuine remount still re-fires
  via a fresh ref). Note: RTL's renderHook does not enable StrictMode's
  effect double-invoke (verified with a probe), so this can't be pinned
  by an automated test here — it's a defensive fix for real dev apps.
- #2 debounceMs robustness: coerce with a finite-number guard
  (Number.isFinite(+debounceMs) ? +debounceMs : 300) so a non-numeric
  string can't collapse the debounce into a 0ms/NaN timer. Identical for
  every valid input (number, numeric string, 0, undefined). Covered by a
  new test that fails on the old code.

Dropped the proposed debounce.flush() timestamp fix: traced it as
unreachable — `timestamp` is always refreshed on the next debounced()
call before later() can fire, so there's no observable bug.

Tests 28 pass, lint + build + e2e green.

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

12 of 12 branches covered (100.0%)

Branch coverage included in aggregate %.

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

67 of 67 relevant lines covered (100.0%)

12.07 hits per line