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 🙏

© 2025 – Pkg Stats / Ryan Hefner

errorify

v0.3.1

Published

Browserify plugin to write failed build error messages to the output file

Downloads

4,265

Readme

errorify

A browserify plugin that writes the error message of a failed build to the output file, rendering it in the browser.

Build Status

Example

watchify index.js -o bundle.js -p errorify

After adding the plugin to your browserify instance, errorify prevents bundle() from emitting error's. All errors are trapped, including: invalid syntax in the source, a missing dependency, a failed transform, etc. When the error message is written to the output file, it is written to the DOM in a <pre> tag (or console.error if we are not in a browser environment).

During development, it might look like this:

es6

Only the bundle() stream is rewritten. If you pass in a callback, it'll get the expected err and body arguments.

errorify is meant to be used with something like watchify. It saves you a trip to the terminal to see why a build failed.

Keep in mind that since errors are no longer emitted, all builds appear "successful". Careful not to deploy broken code.

Note: Only tested with Browserify 9+

Usage

API

var browserify = require('browserify');
var errorify = require('errorify');
var b = browserify({ /*...*/ });
b.plugin(errorify, /* errorify options */);

Options

  • replacer (optional) is a function that takes an error as its first argument, and returns a string that will be used as the output bundle.

CLI

After installing errorify as a local devDependency, you can use the --plugin or -p option like so:

watchify index.js -o bundle.js -p errorify

CSS Customization

The added <pre> tag has the class name errorify, so you can customize errors in your page like so:

body > .errorify {
  color: red;
  font-family: 'Consolas', monospace;
  padding: 5px 10px;
}

License

MIT.