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

react-pending

v1.1.0-a1

Published

Enhancer for React components with pending content

Downloads

5

Readme

react-pending

You’re using pure components, maybe even using stateless functional components. You love them because they keep your code clean:

export function List({ items }) {
  return (
    <ul>
      { items.map(({ title }) => <li>{ title }</li>) }
    </ul>
  );
}

export function ErrorMessage({ error }) {
  return (
    <p class='error'>
      { error }
    </p>
  );
}

However, they expect every prop to be present: rendering this component with undefined/null props will raise an exception. This is common if your content is asynchronously loaded.

react-pending can be used to substitute a different component until the passed props have been loaded. Its declarative API allows render methods to be kept clean, without if statements or ternaries.

In the example below, LoadableList is substituted for List – it accepts the exact same props, but will render with a spinner if items is not yet defined.

import { Component } from 'react';
import pending from 'react-pending';
import Spinner from 'react-spinner';

import { List, ErrorMessage } from './components';

const spinnerUnless = pending(Spinner);

// Will only render using `List` if `items` is present, otherwise renders a spinner
const LoadableList = spinnerUnless(({ items }) => !!items)(List, ErrorMessage);

class ListController extends Component {
  /* ... componentDidMount(), etc ... */

  render() {
    return <LoadableList items={ this.state.items } error={ this.state.errorLoading } />;
  }
}

If you just to want to check for the presence of every prop, pass no arguments to the result of pending():

const spinnerUnlessReady = pending(Spinner)();

// Will only render using `List` if passed props are all ready, otherwise
// renders a spinner
const LoadableList = spinnerUnlessReady(List);

Installation

npm install react-pending --save