2021-10-14
1477
#rxjs#typescript
Emmanuel John
70910
Oct 14, 2021 ⋅ 5 min read

Using RxJS Observables to transform data in TypeScript

Emmanuel John I'm a full-stack software developer, mentor, and writer. I am an open source enthusiast. In my spare time, I enjoy watching sci-fi movies and cheering for Arsenal FC.

Recent posts:

podrocket 2-18

How developer platforms fail (and how yours won’t)

Russ Miles, a software development expert and educator, joins the show to unpack why “developer productivity” platforms so often disappoint.

Elizabeth Becz
Feb 18, 2026 ⋅ 52 sec read
the replay february 18

The Replay (2/18/26): Copilot workarounds, platform pitfalls, and more

Discover what’s new in The Replay, LogRocket’s newsletter for dev and engineering leaders, in the February 18th issue.

Matt MacCormack
Feb 18, 2026 ⋅ 36 sec read
andrew evans claude copilot

Can’t use Claude at work? How I recreated “Skills” in GitHub Copilot

Learn how to recreate Claude Skills–style workflows in GitHub Copilot using custom instruction files and smarter context management.

Andrew Evans
Feb 18, 2026 ⋅ 13 min read

How Ralph makes Claude Code actually finish tasks

Claude Code is deceptively capable. Point it at a codebase, describe what you need, and it’ll autonomously navigate files, write […]

Ikeh Akinyemi
Feb 17, 2026 ⋅ 4 min read
View all posts

2 Replies to "Using RxJS Observables to transform data in TypeScript"

  1. Svelte is a much better system for Observables. It requires setting up its dev tools. As it compiles observable code according to how it is being used.

    With rxjs, never ever use subscribe or unsubscribe yourself. Leave it to a framework such as Angular. Don’t put yourself in a place that a memory leak could happen. Even if it never does. Knockout.js deprecation is a good example why.

  2. Yes, this is something I agree with.
    Managing subscriptions ourselves can be risky because we might forget to unsubscribe from the Observable, resulting in a memory leak.

    Svelte manages our subscriptions on our behalf. This, in my opinion, makes it one of the most reactive frameworks.

    Considering Node.js where there are no native Observables, we are left to manage subscriptions ourselves.

Leave a Reply

Hey there, want to help make our blog better?

Join LogRocket’s Content Advisory Board. You’ll help inform the type of content we create and get access to exclusive meetups, social accreditation, and swag.

Sign up now