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 🙏

© 2026 – Pkg Stats / Ryan Hefner

react-rxjs-connector

v1.0.1

Published

Functions to help react components to respond to RxJS based observables

Readme

Functions to help react components to respond to RxJS based observables

Install

npm install

Run tests

npm run test

Usage

This library currently offers 3 functions to connect RxJS to a React component.

rerenderOnChange

Use rerenderOnChange when connecting a BehaviorSubject to a React component via the componentDidMount lifecycle event. rerenderOnChange will take care of updating your component when the BehaviorSubject changes, as well as unsubscribing when the component unmounts.

Example:

class MyComponent extends React.Component<{ behaviorSubject: BehaviorSubject<string> }> {
    componentDidMount() {
        rerenderOnFieldChange(this, this.props.behaviorSubject);
    }

    render() {
        return <div>{this.props.behaviorSubject.getValue()}</div>;
    }
}

...

const myValue = new BehaviorSubject<string>('initial value');
<MyComponent behaviorSubject={myValue}/>

myValue.next('updated value');

useBehaviorSubject

Use useBehaviorSubject when connecting a BehaviorSubject to a React functional component just as you would a typical React hook. useBehaviorSubject will return the value and a change dispatcher, similar to react hook, allowing you to manipulate the value outside of the React component.

Example:

const MyComponent: React.FC<Props> = ({myBehaviorSubject}) => {
  const [value, setValue] = useBehaviorSubject(myBehaviorSubject);
  
  return (
    <div>
     {value}

      <button onClick={() => setValue('updated value')}>Click Me</button>
    </div>
  )
};

...

const myValue = new BehaviorSubject<string>('initial value');
<MyComponent behaviorSubject={myValue}/>

// Clicking button will make myValue.getValue() equal "updated value"

myValue.next('updated value'); // will cause MyComponent to rerender 

useStore

Use useStore when connecting a "Store" to a React functional component just as you would a typical React hook. A store can be an array of javascript objects, where updating an entity in place may cause React to ignore the update because of it does not check objects with deep equals. useStore will return the value and a change dispatcher, similar to react hook, allowing you to manipulate the value outside of the React component.

Internally, this is different from useBehaviorSubject because the observable's value is converted into a string to encourage react to rerender.

Example:

type Props = {myStore: BehaviorSubject<SomeBigObject[]>};
const MyComponent: React.FC<Props> = ({myStore}) => {
  const [values, setValues] = useStore(mySotre);
  
  return (
    <div>
      <ul>{values.map((v, i) => <li key={i}>{v}</li>)}</ul>

      <button onClick={() => setValue([...values, new SomeBigObject()])}>Click Me</button>
    </div>
  )
};

...

const myStore = new BehaviorSubject<SomeBigObject[]>([{foo: 'bar'}, {foo: 'baz'}]);
<MyComponent behaviorSubject={myStore}/>

// Clicking button will make myStore.getValue() add another object to myStore.

myStore.next([]); // will cause MyComponent to rerender 

Author

👤 Bryan Neva [email protected]

🤝 Contributing

Contributions, issues and feature requests are welcome!Feel free to check issues page. You can also take a look at the contributing guide.

Show your support

Give a ⭐️ if this project helped you!

📝 License

Copyright © 2019 Bryan Neva [email protected]. This project is ISC licensed.


This README was generated with ❤️ by readme-md-generator