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

@vaaas/rx-react

v0.1.9

Published

rxjs utilities for react

Downloads

958

Readme

rxjs utilities for react

event-bus

Provides a centralised event bus for react applications. The intended use case is to support event sourcing in large react applications, decoupling event firing and handling from your store. That way, your store can be dedicated to mutations, while the event bus handlers can issue side-effects (mainly network requests).

Given an event:

class MyEvent {
  constructor(payload) {
    this.payload = payload;
  }
}

Register the event and a handler:

const eventBus = new EventBus();
eventBus.on(
  MyEvent,
  pipe(
    // any rxjs operator, e.g. throttle, debounce...
    map(({ event, dispatch }) => {
      console.log(event.payload);
    }),
  ),
);

return (
  <EventBusProvider value={eventBus}>
    <MyApp />
  </EventBusProvider>
);

Then, in any react component:

function MyComponent() {
  const eventBus = useEventBus();
  function onClick() {
    eventBus.dispatch(new MyEvent("hello, world!"));
  }
  return <button onClick={onClick}>Click me</button>;
}

If you have several related event handlers, you can register them in batches through installers:

function MyInstaller(eventBus: IEventBus): IEventBus {
  return eventBus
    .on(SomeEvent, someHandler)
    .on(AnotherEvent, anotherHandler)
    .on(ThirdEvent, tertiaryHandler);
}

const eventBus = new EventBus().install(MyInstaller);

Handlers can be registered dynamically and asynchronously as needed. If you have a lot of handlers, you don't need to register all of them upfront, and separate modules can plug their own handlers and events into the central event bus after loading.

hooks

React hooks for bridging rxjs observables into the React lifecycle.

useSubject

Creates a stable Subject and a callback to push values into it. Useful for turning event handlers into observable sources.

function SearchBox() {
  const [input$, onInput] = useSubject<string>();
  // input$ is an Observable<string> you can pipe further
  return <input onChange={(e) => onInput(e.target.value)} />;
}

useEffectStream

Emits the dependency array as an observable whenever any dependency changes.

function UserProfile({ userId }: { userId: string }) {
  const deps$ = useEffectStream([userId]);
  // deps$ emits [userId] every time userId changes
}

usePipe

Applies an rxjs operator pipeline to a source observable once, returning a stable reference.

const debounced$ = usePipe(input$, pipe(debounceTime(300)));

useSubscription

Subscribes to an observable for the lifetime of the component, unsubscribing on unmount.

useSubscription(clicks$, (event) => {
  console.log("clicked", event);
});

useLatestState

Turns an observable into React state, re-rendering on each emission.

function Counter({ count$ }: { count$: Observable<number> }) {
  const count = useLatestState(count$, 0);
  return <span>{count}</span>;
}