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-badly

v1.0.12

Published

Error boundary react component

Downloads

100

Readme

react-badly

Take hold of your react lifecycle hooks with react-badly

npm version

You can install off of npm with

npm install react-badly

# or yarn

yarn add react-badly

This component is a wrapper for any of your React 16+ plus components that may have an error in them.

How to use

The simplest way is to just wrap any component that you think may error with ReactBadly

This will prevent the component from rendering (also will stop any children in the tree as well). This is to make sure that your whole component tree does not dismount as React 16+ does.

import ReactBadly from 'react-badly';


// some code later on

<ReactBadly>
  <SomeComponentThatMayHaveAnError>
    ...
  </SomeComponentThatMayHaveAnError>
</ReactBadly>

If you want to handle your error with some functionality (like sending to analytics etc) you can pass an onError property which will get the error and any info as parameters from react.

import ReactBadly from 'react-badly';

const errorFunction = (error, info) => {
  // can handle the error here and do what you will with it
};

// some code later on

<ReactBadly onError={errorFunction}>
  <SomeComponentThatMayHaveAnError>
    ...
  </SomeComponentThatMayHaveAnError>
</ReactBadly>

There may also be some cases where you actually want to render something else to display if there was an error instead of just not displaying anything. To do that you can pass the render property which will accept a function that will take in { error, info } as a parameter. This will render instead of the direct child of ReactBadly.

import ReactBadly from 'react-badly';

const renderError = ({ error, info }) => (
  <React.Fragment>
      <h2>You have an error!</h2>
      <pre>{JSON.stringify(error)}'\n'{JSON.stringify(info)}</pre>
  </React.Fragment>
);

// some code later on

<ReactBadly render={renderError}>
  <SomeComponentThatMayHaveAnError>
    ...
  </SomeComponentThatMayHaveAnError>
</ReactBadly>