Packages

What to use instead

A better maintained package

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

The list compares the options for execa: 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

No release read yet.

Dependency tracking · free for 3 projects

Know when your own dependencies move

This page watches execa. 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 28 Oct 2026.