toObservable() — How to Bridge Angular Signals and RxJS

toObservable() — Bridging the Gap Between Angular Signals and RxJS If you've been working with Angular Signals, you've probably hit this wall at some point. You have a Signal — maybe a search input, maybe a selected filter from a dropdown — and you need to debounce it . Or switchMap it. Or pipe it through a chain of RxJS operators before sending it to an API. And then you realise: Signals don't have debounceTime . They don't have switchMap . They live in a completely different reactive world. That's where toObservable() comes in. It's the reverse bridge — and once you understand how it works, the combination of Signals and RxJS becomes genuinely powerful. The Context: Two Reactive Worlds Angular 16+ ships with two reactive primitives that serve different purposes: Signals — synchronous, pull-based, zero boilerplate. Perfect for local component state and template bindings. No subscriptions, no cleanup, no async pipe. Observables (RxJS) — asynchronous, push-based, operator-rich. Perfect