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

inh

v0.0.1

Published

DEPRECATED, see README.md Was: both browser- and node-friendly inherits() for browserify

Downloads

3

Readme

inh

ATTENTION This package is deprecated and is no longer supported. Please, use Isaac's inherits package instead.

The Story

The idea listed below have been moved to inherits package version 2.0 (and above) to have exactly one canonical 'inherits' package and don't confuse people by having two options.

The Idea

inherits for browserify

inherits function is used in almost every module. It is located in util package and browserify provides you browser-adapted shim of this package. It's good, but the shim is very large, because:

  • it contains polyfill to make inherits work with old browsers
  • it contains a lot of unrelated stuff
  • it contains the shim for process global, because this unrelated stuff depends on it

browserify produces a lot of supportive code for util package. It is ok for large projects, but too much for tiny libraries.

inh is aimed to solve this problem. For node.js it just returns standard inherits implementation from util package, but for browserify it provides browser-specific version (using "browser" key in package.json).

It's recommended to use inh in all your code that can be used on client side.

Usage

npm install inh and then use

var inherits = require('inh');

instead of

var inherits = require('util').inherits;