Packages

inherits

2.0.4 · 19 Jun 2019ISC285.1M / weekRepositoryHomepagenpmAtom feed

Your version

Where each line stands

Plan an upgrade
  • 2.x2.0.4No known advisoryLatest line
  • 1.x1.0.2No known advisoryTo 2.0.4

What to use instead

Built into the platform

From the e18e module-replacements list, maintained by the community.

Use Use native class syntax, built into Node 6.0.0 and later.

Before you switch

  1. 1

    Check what else depends on it

    Paste your package.json in the dependency check to see every deprecated or outdated package in one pass, not only this one.

  2. 2

    Read the replacement's peers and releases

    A native API or a few lines of code need no release notes, but check the Node version your project runs on.

  3. 3

    Know when it ships

    Follow the new package on inlinr: its releases and advisories land in your feed, and the time spent on the migration branch shows on its page.

Latest releases

  1. 2.x · latest line
  2. 2.0.4

    19 Jun 2019
  3. 2.0.3

    8 Sep 2016
  4. 2.0.2

    7 Sep 2016

Notes older than 90 days are read on the Releases tab.

Dependency tracking · free for 3 projects

Know when your own dependencies move

This page watches inherits. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.

  • Advisories reach you

    An email when a critical or high advisory affects a project, before the next install.

  • Upgrades checked first

    Peer ranges, Node, ESM-only and types changes read before you bump.

  • Only what matters

    Majors and breaking notes stay; patches and sibling bumps fold into one line.

How dependency tracking works

Reading releases, release notes and advisories…

Registry facts last checked 3 Nov 2026. Releases and advisories last read 3 Nov 2026.