npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@wishtack/rx-scavenger

v2.0.1

Published

RxJS Subscription Garbage Collector + Angular `ngOnDestroy` hook.

Downloads

924

Readme

Build Status Greenkeeper badge

What is rx-scavenger?

rx-scavenger is an RxJS Subscription Garbage Collector.

Its main goal is to reduce the boilerplate code when handling RxJS Subscriptions in Angular components in an easy and safe way.

rx-scavenger also allows you to map Subscriptions to a key and every time that you subscribe to a new Observable using the same key, the previous Subscription will automatically be unsubscribed of.

This easily avoids some race conditions and memory leaks when overwriting Subscriptions.

Getting Started

Install

yarn add @wishtack/rx-scavenger

or npm install --save @wishtack/rx-scavenger

Usage in an Angular component

import { Scavenger } from '@wishtack/rx-scavenger';

@Component({
    ...
})
export class WeatherComponent implements OnDestroy, OnInit {
    
    private _scavenger = new Scavenger(this);
    
    constructor(private _weatherStation: WeatherStation) {
    }
    
    ngOnInit() {
        
        this._weatherStation
            .getWeather('Lyon')
            .pipe(
                this._scavenger.collect()        
            )
            .subscribe(weather => {
                ...
            });
        
    }
    
    ngOnDestroy() {
    }
    
}

As you can see, there's no need to call Scavenger.unsubscribe() in ngOnDestroy() method as the Scavenger class takes care of implementing it and collecting every Subscription to the Observable returned by WeatherStation.getWeather() using the Scavenger.collect() method.

Using collectByKey to avoid overwritten Subscriptions

    refreshWeather(city) {
        
        this._subscription = this._weatherStation
            .getWeather(city)
            .subscribe(weather => {
                ...
            });
        
    }

Usually, if the WeatherComponent.refreshWeather() method here is called more than once, we might end up in a race condition or simply overwrite the Subscription in _subscription property.

Race condition issues also happen when using takeUntil(destroyed$) pattern.

Using the Scavenger.collectByKey(key: string) method, the first Subscription is stored in a Map with that key and on the second subscribe, the first Subscription is unsubscribed from so there's only one Subscription open with that key at a time.

    refreshWeather(city) {
        
        this._weatherStation
            .getWeather(city)
            .pipe(
                this._scavenger.collectByKey('weather')        
            )
            .subscribe(weather => {
                ...
            });
        
    }

Manual Unsubscribe

You can also unsubscribe from all the collected Subscriptions using Scavenger.unsubscribe().