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

redux-suspense

v0.0.5

Published

npm install redux-suspense

Downloads

9

Readme

Redux Suspense

npm install redux-suspense

Motivation

This project is an experiment that aims at finding a way to integrate existing data flow (built with Redux) with upcoming React Suspense feature. The idea behind proposed implementation is to reduce the amount of imperative logic required for coupling Redux store to data fetched from the server side.

A components reads data from store in the same synchronous way as before. If data is not available (not yet fetched) in the rendering phase, an effect is thrown out of component so React suspend the render till the effect (scheduled data fetching) is complete. After, React renders the component again with necessary data available in store.

The important part of the mechanism is that developers do not need to specify such logic in componentDidMount() explicitly as it is needed now. However, the top-level logic remains the same. Current implementation hides this aspect from developers so it can be done in the most efficient way and updated with newer versions of React without forcing developers to refactor existing code.

Note: this project is an experiment. I encourage you to try, though carefully consider undiscovered bugs before using in your real projects.

API

import { createResourceMapper } from 'redux-suspense';

Resource mapper combines a state selector function and action creator in order to provide frictionless method to query async data from store.

import { connectSuspense } from 'redux-suspense';

Suspense connector is a HOC built on top of connect() in order to inject the state tree and dispatch function that is going to be used by a resource mapper.

import { Consumer } from 'redux-suspense';

The same connector as connectSuspense() but done with render prop pattern instead of higher-order component.

import { Placeholder } from 'redux-suspense';

A component wrapper that allows to show alternative content if async children can't render their content in defined time frame.

Examples

In examples folder you can find Reddit API Example which is basically an original advanced example improved by redux-suspense. In addition, Basic Example shows the minimal code implementation with tests.