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:

Crud Rest Api With Node Js Express And Postgresql

CRUD REST API with Node.js, Express, and PostgreSQL

Build a CRUD REST API with Node.js, Express, and PostgreSQL, then modernize it with ES modules, async/await, built-in Express middleware, and safer config handling.

Tania Rascia
Mar 25, 2026 ⋅ 16 min read
the replay march 25

The Replay (3/25/26): Senior dev hiring woes, what AI agents miss, and more

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

Matt MacCormack
Mar 25, 2026 ⋅ 29 sec read
emmanuel john senior dev hiring

The hidden skills gap in senior dev hiring (and how to screen for it)

Discover a practical framework for redesigning your senior developer hiring process to screen for real diagnostic skill.

Emmanuel John
Mar 25, 2026 ⋅ 12 min read

Does the Speculation Rules API boost web speed? I tested it

I tested the Speculation Rules API in a real project to see if it actually improves navigation speed. Here’s what worked, what didn’t, and where it’s worth using.

Jude Miracle
Mar 24, 2026 ⋅ 10 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

Your email address will not be published. Required fields are marked *

Would you be interested in joining LogRocket's developer community?

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