</>PackageGraphPackageGraph

inherits

npmv2.0.4

Browser-friendly inheritance fully compatible with standard node.js inherits()

Not recommended for new projects

No — inherits should not be adopted for new projects. Last published 2639 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 2639 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 3.9 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    ISC — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding inherits to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

3.9 KB
Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the inherits README.

var inherits = require('inherits');
// then use exactly as the standard one

inherits vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
inheritsthis page01ISC7 years ago
isarray174.9M3MIT1 day ago
open130.4M4MIT1 day ago
axios106.5M4MIT1 day ago
loose-envify65M2MIT1 day ago
fflate53.5M1MIT1 day ago

Dependencies

Declared by inherits v2.0.4. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (1)

tap ^14.2.4

Used by

Popular packages that depend on inherits.

Relationship graph

Dependencies (left) and dependents (right) of inherits.

http-errorsinherits
inherits dependencies dependents

Frequently installed together

Release history

No releases in the last two years, typically about 737 days apart.

Recent versions of inherits
VersionPublishedSizeLicense
2.0.4latest7 years ago3.9 KBISC
2.0.310 years agoISC
1.0.211 years agoISC
1.0.111 years agoISC
2.0.113 years agoISC
2.0.013 years agoWTFPL2
1.0.015 years agoISC

Overview

inherits is an npm package that browser-friendly inheritance fully compatible with standard node.js inherits(). It has 1 known dependents in the graph. The latest version is 2.0.4, released under the ISC license.

Who should use it

Teams working in the npm ecosystem who need browser-friendly inheritance fully compatible with standard node.js inherits() and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (ISC).
  • Lean dependency tree (1 direct dependencies).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Frequently asked questions

Should I use inherits?

No — inherits should not be adopted for new projects. Last published 2639 days ago.

How do I install inherits?

Run `npm install inherits` to add inherits to your npm project.

What license is inherits released under?

inherits is distributed under the ISC license.

How popular is inherits?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on inherits.

Is inherits still maintained?

The most recent release of inherits (v2.0.4) was published 7 years ago.

Does inherits run install scripts?

No. inherits does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.