npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2022 – Pkg Stats / Ryan Hefner




A redbox (rsod) component to display your errors.





Build Status semantic-release

The red box (aka red screen of death) renders an error in this “pretty” format:


Catch an error and give it to redbox-react. Works great with

or manually:

import RedBox from 'redbox-react'

const e = new Error('boom')
const box = <RedBox error={e} />

Here is a more useful, full-fleged example:

/* global __DEV__ */
import React from 'react'
import { render } from 'react-dom'
import App from './components/App'

const root = document.getElementById('root')

if (__DEV__) {
  const RedBox = require('redbox-react').default
  try {
    render(<App />, root)
  } catch (e) {
    render(<RedBox error={e} />, root)
} else {
  render(<App />, root)

What Is This Good For?

An error that's only in the console is only half the fun. Now you can use all the wasted space where your app would be if it didn’t crash to display the error that made it crash.

Please use this in development only.

Will this catch errors for me?

No. This is only a UI component for rendering errors and their stack traces. It is intended to be used with with other existing solutions that automate the error catching for you. See the list at the top of this document or take a look at the examples.

Optional Props

The RedBox component takes a couple of props that you can use to customize its behaviour:

editorScheme [?string]

If a filename in the stack trace is local, the component can create the link to open your editor using this scheme eg:

  • subl to create subl://open?url=file:///filename.
  • or vscode to create vscode://file/filename.

useLines [boolean=true]

Line numbers in the stack trace may be unreliable depending on the type of sourcemaps. You can choose to not display them with this flag.

useColumns [boolean=true]

Column numbers in the stack trace may be unreliable depending on the type of sourcemaps. You can choose to not display them with this flag.

style [?object]

Allows you to override the styles used when rendering the various parts of the component. It will be shallow-merged with the default styles.

If you’re using react-transform-catch-errors you can add these options to your .babelrc through the imports property.

Sourcemaps With Webpack

If you’re using Webpack you can get accurate filenames in the stacktrace by setting the output.devtoolModuleFilenameTemplate settings to /[absolute-resource-path].

It's recommended to set the devtool setting to 'eval'.