rx-effects-1.4.0

Reworked rxEffect lifecycle handling, plus corrected package metadata.

Fixes

• Source errors are no longer swallowed silently. When rxEffect is used with only a destroyRef (no injection context), no Angular ErrorHandler is available. Errors from a source observable previously disappeared without a trace — the effect just died. They are now reported via console.error. Other effects on the same instance keep running, and the host app is unaffected.
• Cleanup ordering reworked: onCleanUp now runs exactly once, whether triggered by a manual cleanUp() or by instance destroy — whichever comes first.
• Effects registered before a throwing setupFn no longer leak; they are cleaned up before the error is rethrown.
• After the instance is destroyed, run() is a reliable no-op and a passed Subscription is unsubscribed immediately.

Package metadata

• peerDependencies now declare rxjs: ^7.4.0. This was previously undeclared. The library imports tap/catchError from the rxjs root, which only exists in RxJS 7+ — so this documents an already-existing requirement rather than introducing a new one. If you are on RxJS 6, you will now see a peer warning; the library never worked on RxJS 6.
• @angular/common removed from peerDependencies — it was never used by the library.
• @angular/core peer range narrowed to >=16.0.0 <23.0.0.

Other

• All public types (EffectCleanUpRef, RunOptions, RxEffect, EffectsSetupFn) are exported from the package root.
• Error handling and cleanup semantics documented in the README.
• Demo app now uses rxEffect for real, with an e2e smoke spec.

Full changelog: rx-effects-1.3.0...rx-effects-1.4.0

rx-effects-1.3.0

Features

• feat(effects): add effects factory function to manage subs (7254e4f)
• feat(effects): enhance options to pass a DestroyRef (bcd1702)
• feat(effects): provide a clean up function for a single effect (45c9ba3)