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

@vanya2h/utils-rxjs-react

v0.8.0-rc.1

Published

React hooks and components for RxJS observables

Readme

@vanya2h/utils-rxjs-react

React bindings for RxJS — hooks and components for consuming Observable<T> / BehaviorSubject<T> in React without boilerplate.

Why

The main benefit is late unwrapping. Instead of subscribing at the top of the tree and threading the resolved value through props, pass the Observable<T> down and let it unwrap at the leaf that actually renders it. Re-renders stay scoped to the components that consume the value — parents and siblings don't repaint when the data changes. In practice this turns "everything re-renders when the store updates" into "only the cell that reads this field re-renders," which adds up across a real-world React app.

Install

pnpm add @vanya2h/utils-rxjs-react react rxjs

Peer deps: react ^18 || ^19, rxjs ^7.

API

useObservable(observable$, initialValue)

Concurrent-safe subscription built on useSyncExternalStore. Returns initialValue until the first emission, then the latest emitted value. Single subscription per mount; re-subscribes when the observable identity changes.

const count = useObservable(count$, 0);

usePending(source$, getDefaultValue?)

Wraps any ObservableLike<T> (an Observable<T> or a plain T) into a { status: "pending" | "fulfilled" | "rejected" } state machine. The rejected shape exposes onReload for retry.

const status = usePending(user$);

if (status.status === "pending") return <Spinner />;
if (status.status === "rejected") {
  return <button onClick={status.onReload}>Retry</button>;
}
return <div>{status.value.name}</div>;

<Pending value$={...}>

Component sugar over usePending. Picks one of the pending / rejected / children render-props based on the current status.

<Pending
  value$={user$}
  pending={<Spinner />}
  rejected={({ error, onReload }) => <ErrorView error={error} onRetry={onReload} />}
>
  {(user) => <UserCard user={user} />}
</Pending>

<BehaviorSubjectRender value$={...}>

Subscribes to a BehaviorSubject<T> and re-renders children with the latest value. Skips the initial buffered emission (already used as initial state) and deduplicates with distinctUntilChanged.

<BehaviorSubjectRender value$={counter$}>
  {(n) => <span>{n}</span>}
</BehaviorSubjectRender>

<OnlyIfTruthy value$={...}>

Renders the child only when the resolved value is truthy. The render-prop receives the value narrowed to TruthyTypesOf<T>.

<OnlyIfTruthy value$={maybeUser$}>
  {(user) => <UserCard user={user} />}
</OnlyIfTruthy>

render(data, renderable)

Low-level helper used by the components above: invokes a function renderable with data, or returns the static ReactNode.