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

v0.0.3

Published

A simple error boundary for React

Downloads

3

Readme

React Error Boundary with Custom Logger

This project is a React application with an integrated error boundary that logs errors to the console and posts them to Jsonbin.io for further analysis.

Features

  • Error Boundary to catch JavaScript errors anywhere in the component tree.
  • Custom logger to log errors to the console and send them to Jsonbin.io.
  • Custom error handling for both caught and uncaught errors in React 19.

Installation

  1. Clone the repository:

    git clone https://github.com/yourusername/react-error-boundary-logger.git
    cd react-error-boundary-logger
  2. Install the dependencies:

    npm install

Configuration

  1. Open src/logger.ts and replace YOUR_JSONBIN_MASTER_KEY with your actual Jsonbin.io master key.

     REACT_APP_API_ENDPOINT=https://api.jsonbin.io/v3/b
     REACT_APP_API_KEY= # Add Valid Key, Required
     REACT_APP_ADMIN_KEY=# Add Valid Key, Required
     REACT_APP_BIN_NAME=# Add Valid Bin Name, Not Required
     REACT_APP_BIN_PRIVATE=# Add true or false, Not Required
     REACT_APP_COLLECTION_ID=# Add Valid Collection ID, Not Required

Usage

  1. Start the development server:

    npm start
  2. The application will be available at http://localhost:3000.

Project Structure

  • src/: Contains the source code of the React application.
    • App.tsx: The main application component.
    • ErrorBoundary.tsx: The Error Boundary component to catch and log errors.
    • logger.ts: The custom logger utility to log errors to the console and send them to Jsonbin.io.
    • index.tsx: The entry point of the React application.

Error Logging

The custom logger logs errors in the following format:

{
  "error": {
    "errorInfo": "",
    "errorMessage": "",
    "timestamp": ""
  },
  "metadata": {
    "created": "",
    "component": null
  }
}

Example

To see the error logging in action, introduce an error in any component, for example, in App.tsx:

function App() {
  // This will throw an error
  throw new Error('Test error');
  return (
    <div className="App">
      <h1>Welcome to the App</h1>
    </div>
  );
}

This will trigger the error boundary and log the error to the console as well as send it to Jsonbin.io.

License

This project is licensed under the MIT License - see the LICENSE file for details.