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

react-rx-connect

v1.1.1

Published

A small lightweight helper to connect RxJS observables to react component state.

Downloads

2

Readme

react-rx-connect build status

A small lightweight helper to connect RxJS observables to react component state.

install

npm i react-rx-connect --save

Problem

When using streams in React it's quite annoying to do manual subscribes and unsubscribes. When the component gets destroyed we have to unsubscribe all subscriptions to avoid memory-leaks. This results in messy code. The code below is an example of a dirty, redundant rx maintainance.

export class SomeComponent extends React.Component<any, any> {
    subscriptions = []; // some variable to manage the subscriptions
    state = {
        foo: null,
        bar: null
    };

    componentDidMount(): void {
        // subscribe manually => annoying
        // set the state manually => annoying
        // keep track of the subscriptions => annoying
        this.subscriptions.push(Observable.of('foo').subscribe(val => this.setState({foo: val})));
        this.subscriptions.push(Observable.of('bar').subscribe(val => this.setState({bar: val})));
    }
    
    // when the component gets destroyed, manually unsubscribe all subscriptions => annoying
    componentWillUnmount(): void {
        this.subscriptions.forEach(sub => sub.unsubscribe());
    }

    render(): any {
        return (
            <div>
                <h1>Gifs</h1>
                {this.state.foo}
                {this.state.bar}
            </div>
        )
    }
}

How to use react-rx-connect

The connectStreams function will take an object of streams as the second parameter. It will automatically update the state whenever a value in one of the streams changes. When the component get's destroyed it will also automatically unsubscribe to avoid memory leaks.


export class SomeComponent extends React.Component<any, any> {
    state = {
        foo: null, // this will be set based on some stream
        bar: null // this will be set based on some stream
    };

    componentDidMount(): void {
        // pass a number of observables to the connectStreams
        connectStreams(this, {
            foo: Observable.of('foo'),
            bar: Observable.of('bar')
        });
    }

    render(): any {
    	// since the state is updated by the connectedStreams function
    	// the values foo and bar will be available here, and automatically 
    	// updated
        return (
            <div>
                <h1>Gifs</h1>
                {this.state.foo} 
                {this.state.bar}
            </div>
        )
    }
}

We reduced the redundant messy code, to one line now.