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 🙏

© 2026 – Pkg Stats / Ryan Hefner

monobrow

v2.11.0

Published

Browserify with opinions

Readme

monobrow

browserify, with opinions.

Install

First add to your project:

npm install --save-dev monobrow

Quick start

After installing, run npx monobrow init

This will:

  • create a config file with default settings (monobrow/config.js)
  • add some aliases to your package.json scripts

Editing config by hand

Monobrow config is just a js module that exports an object. For example, a simple one looks like this:

// your-project/monobrow/config.js

module.exports = {
  entry: 'src/index.js',
  output: {
    dir: 'build'
  }
}

Then add a script to your package.json:

"scripts": {
  "build": "monobrow"
}

And npm run build

You can also npm run build -- -w to watch, or npm run build -- -h to hot-reload.

You can also specify hostname for the hot reload server: npm run build -- -h 127.0.0.1. If you supply -h (or --hot) with no value, the default hostname of 0.0.0.0 is used.

Simple bundle splitting

Any packages listed in the vendor array will be split into a separate bundle. The default name is vendor.js, but can be specified in the output.vendor option. Eg.

// your-project/monobrow/config.js

module.exports = {
  entry: 'src/index.js',
  output: {
    dir: 'build'
  },
  vendor: [
    'react',
    'react-dom',
    'classnames'
  ]
}

This will produce 2 files in the build directory:

  • build/index.js: just your application bundle
  • build/vendor.js: a bundle with externalized vendor files

When you do this, don't forget to add a new <script src="build/vendor.js"></script> to your page, before the <script> tag that includes your application bundle.

Vendor files provided by packs

Packs can provide a prebuilt bundle of vendor modules. Eg.

// your-project/monobrow/config.js

module.exports = {
  entry: 'src/index.js',
  output: {
    dir: 'build',
    vendor: 'vendor.js'
  },
  packs: [
    require('monobrow-react-pack')
  ]
}

Tech

Example

Take a look at monobrow-todomvc to see a simple example of:

  • splitting app code and dependencies into separate bundles
  • adding transforms (eg. babelify)

License

MIT