Packages

find-up

8.0.0 · 16 Sep 2025MIT421M / weekRepositoryHomepagenpmAtom feed

Your version

Where each line stands

Plan an upgrade
  • 8.x8.0.0No known advisoryLatest line
  • 7.x7.0.0No known advisoryTo 8.0.0
  • 6.x6.3.0No known advisoryTo 8.0.0
  • 5.x5.0.0No known advisoryTo 8.0.0
  • 4.x4.1.0No known advisoryTo 8.0.0
  • 3.x3.0.0No known advisoryTo 8.0.0

What to use instead

A better maintained package

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

The list compares the options for find-up: read the comparison.

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. 8.x · latest line
  2. 8.0.0

    16 Sep 2025
  3. 7.x · maintenance
  4. 7.0.0

    16 Nov 2023
  5. 6.x · maintenance
  6. 6.3.0

    8 Feb 2022

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 find-up. 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.