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

suspense-datasource

v0.0.5

Published

React Suspense compatible state management solution to segregate application and UI data.

Downloads

34

Readme

Suspense Datasource

suspense-datasource is a library that aims to be a more organized way to store and manage backend originated application data in React. It helps the developer to separate application logic state from UI state, and also provide primitives to manage this externally loaded data.

It is made to be used in conjunction with <Suspense> where it provides a get(key) function to load the dataset that can be passed directly into a component in the Suspense's component context.

How to use it

To define a new externally loaded dataset first you need to create a class that extends the class Datasource and in the newly created class override the fetch(key) method with the instructions to make the network calls to fetch your data.

The magic happens when you define your specific methods inside your class to manipulate your state, concentrating your business rules in a place separated from the UI definition.

There's also a reset(key) method to reset the data contained under that key and reset() to reset all the data.

Example

Here's a simple example on how to use it where a datasource is defined with a cache invalidation rule that makes the fetched data expire after 10 seconds.

The class definition:

export class AlbumDatasource extends Datasource {
    async fetch(key){
        const albums = getAlbums(`/${key}/albums`);
        
        setTimeout(() => {
            this.reset(key)
        }, 10_000)

        return albums;
    }
}

Then it is added as an operation inside the context:

const RootContext = createContext(null);

const albumDatasource = new AlbumDatasource();

function getAlbums(artistId) {
  return albumDatasource.get(artistId);
}

export function ContextProvider(props) {
  return (
    <RootContext.Provider
      value={{
        getAlbums
      }}
    >
      {props.children}
    </RootContext.Provider>
  );
}

export function useProvider() {
  const maybeContext = useContext(RootContext);
  if (!maybeContext) throw new Error("invalid application context");

  return maybeContext;
}

And how you would call it inside the UI code:

export default function Albums({artist}) {
  const provider = useProvider();
  return (
    <ul>
      {provider.getAlbums(artist.id).map(album => (
        <li key={album.id}>
          {album.title} ({album.year})
        </li>
      ))}
    </ul>
  );
}
export default function ArtistPage({ artist }) {
  return (
    <>
      <h1>{artist.name}</h1>
      <Suspense fallback={<Loading />}>
        <Albums artist={artist}/>
      </Suspense>
    </>
  );
}