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

react-renderer-status-split

v0.1.0

Published

React Component helps to split render.

Readme

React Component helps to split render.

npm

Install

yarn add react-renderer-status-split

or

npm i -S react-renderer-status-split

Usage

Component is designed to avoid deep ternary in components. You can set renders you want to handle for your action. Check simple list with all types of renders:

import { RendererStatusSplit } from 'react-renderer-status-split'

function MyComponent() {
  const statuses = {
    isLoading: false,
    error: "",
    isDone: false,
  };

  return (
    <RendererStatusSplit
      statuses={statuses}
      renderPreview={() => <div>action not started</div>}
      renderLoading={() => <div>action is loading</div>}
      renderError={(error) => <div>action errored: {error}</div>}
      renderEmpty={() => <div>no data after action</div>}
      render={() => <div>show data</div>}
    />
  )
}

Props

  • statuses required

    • isLoading optional - (Boolean)
    • isDone optional - (Boolean) Defines if action is completed
    • data optional - (any) Defines if some data was received after action. Will be used for renderEmpty
    • error optional - (String) check if action was completed with error, so it will try to select renderError()
  • isEmpty optional - (Boolean) - Designed for force setting if data exists or not. If isEmpty is set to false, it will skip all status renders.

  • render(data) required - Always default render. Other renders can replace this one for specific statuses. Ideally if all renders exists, this one will be visible only when action is completed and data exists.

  • renderLoading() optional - means action in progress. Checks if isLoading is true

  • renderEmpty() optional - means action is completed, but data is empty. Checks if data is empty. Or isEmpty is true.

  • renderError(error) optional - means action is errored. will be used when error is not empty

  • renderPreview() optional - means action is not started yet.

Advanced usage

Composition example using: api, redux, react-hooks-async-handlers

import { RendererStatusSplit } from 'react-renderer-status-split'
import { useAsyncFetch } from 'react-hooks-async-handlers'


function MyComponent() {
  const dispatch = useDispatch()
  const { pageObject } = useSelector((state) => ({
    pageObject: state.pageObject,
  }))
  
  const fetchAction = useAsyncFetch(
    async () => {
      await dispatch(Dispatcher.getPageObject())
    },
    { maxTries: 3 },
  )
    
  return (
    <div>
      <h1>Page Title</h1>
  
      <div className={'content-container'}>
        <RendererStatusSplit
          statuses={fetchAction}
          isEmpty={_.isEmpty(pageObject)}
          renderPreview={() => <div>Loading will start soon</div>}
          renderLoading={() => <div>Component is loading</div>}
          renderError={(error) => <span color={'red'}>{error}</span>}
          renderEmpty={() => <div>Component is not found</div>}
          render={() => <ComponentInfo data={pageObject} />}
        />
      </div>
    </div>
  ) 
}

See Also

List of libraries that work well with status renderer: