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

@isumix/react-exception

v1.0.4

Published

A flexible React's Error Boundary implementation

Downloads

8

Readme

@isumix/react-exception

A flexible React's Error Boundary implementation

Available since React 16.6. Works with React Native.

Description

You should enclose your components within Error Boundary, so users will be presented with a fallback view in case of failure.

<Exception fallback="An error has occurred!">
  <Components/> could throw exceptions
</Exception>

The <Exception> component will catch any errors thrown in the inner components' lifecycle methods.

Error boundaries do not catch errors for: event handlers, asynchronous code and SSR. See useEventThrow below for solution.

Install

npm install --save @isumix/react-exception
yarn add @isumix/react-exception

Example

Play with web example in codesandbox.io

Play with native example in snack.expo.io

import * as React from "react";
import { Exception } from "@isumix/react-exception";

const ComponentWillThrow = () => {
  throw "BOOM!";
};

export default () => (
  <Exception fallback={<i>Something went wrong!</i>} >
    <ComponentWillThrow />
  </Exception>
);

Exception

<Exception
  fallback="optional: Text or <Node /> or Component"
  onError="optional: error handler function"
>
  Child <components/> that could throw exceptions
  Including <Exception>nesting</Exception>
</Exception>

fallback

If no fallback is provided the error will be rethrown

const fallbackString = 'An error has occurred!';
const fallbackNode = <strong>An error has occurred!</strong>;
const FallbackComponent = ({ error, reset }: ExceptionFallbackProps) => (
  <b style={{ color: "red" }}>
    An error "{error.message}" has occurred!
    <button type="button" onClick={reset}>
      Reset
    </button>
  </b>
);

onError

const handleError: ExceptionErrorHandler = (error, errorInfo) => console.log(error, errorInfo);

useEventThrow

In event handlers and asynchronous code, you can useEventThrow hook to be able to catch exceptions in Error Boundary.

Available since React 16.8

import { useEventThrow } from "@isumix/react-exception";

const ComponentWillThrow = () => {
  const eventThrow = useEventThrow();
  return (
    <p>
      Some text
      <button type="button" onClick={() => eventThrow("BANG!")}>
        Throw
      </button>
    </p>
  );
};

Please note: for asynchronous code, there is a better approach

<Exception fallback="Rejected">
  <Suspense fallback="Pending">
    <CustomComponent /> has asynchronous code and could throw exceptions
  </Suspense>
</Exception>