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

browserinc

v1.1.0

Published

Change browser fields of dependent packages as a postinstall hook

Readme

BrowserInc

Used as a postinstall hook, this command-line utility can be used to re-include browserify excludes (including those specified in dependent packages).

Why?

There are certain situations in which the --no-browser-field browserify flag is not accurate enough. Where one is running a browserified package in a specialized environment (eg. Chrome extension/app) and wants to exclude only certain parts of the browser field across multiple package dependencies.

This is where browserinc comes in.

Installation

npm install browserinc

Usage

What browserinc essentially does is edit the dependent package.json files of the root module and removes undesired browser-field excludes from them (thus including them).

The easiest way to use browserinc would be to include it as a postinstall hook in your package.json eg.:

"scripts": {
  "postinstall": "browserinc"
}

In the same file, be sure to add a "browserinc" field with an "include" array that would specify which packages/files you'd like to include. eg.:

"browserinc": {
  "include": [
      "package1",
        "./path/to/specific/file"
    ]
}

Issues / Contributions

If anything is broken or you'd like some behaviour changed, I would very much welcome your issues or PRs.

License

MIT