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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@workingmodel/why-wont-this-install

v1.0.0

Published

Diagnoses why npm install is failing and tells you in plain English how to fix it.

Readme

@workingmodel/why-wont-this-install

Diagnoses why npm install is failing and tells you in plain English how to fix it. Developed by Working Model.

npm version npm downloads license

$ why-wont-this-install

why-wont-this-install — scanning /your/project

✖ ERROR  Engine mismatch
  Your Node version (18.4.0) doesn't satisfy the required range: >=22.0.0
  Fix: Install Node >=22.0.0 via nvm: `nvm install 22`

✖ ERROR  Conflicting lock files
  Multiple lock files found: package-lock.json, yarn.lock
  Fix: Pick one package manager and delete the other lock file(s).

2 errors found.

Install

npx @workingmodel/why-wont-this-install

Or install globally:

npm install -g @workingmodel/why-wont-this-install

Usage

Run from your project directory:

why-wont-this-install

Or point it at a specific path:

why-wont-this-install /path/to/project

What it checks

| Check | What it catches | |---|---| | Engine mismatch | Node or npm version doesn't satisfy engines field | | Conflicting lock files | Multiple package managers have touched the project | | Lock file version | package-lock.json lockfileVersion requires a newer npm | | Wrong package manager hint | yarn.lock or pnpm-lock.yaml present but you're running npm | | Permission error | node_modules is not writable by the current user | | Platform mismatch | Package's os field excludes your operating system | | CPU mismatch | Package's cpu field excludes your architecture | | Custom registry | npm is pointed at a non-default registry | | Corrupted install | node_modules exists but install markers are missing | | No package.json | You're in the wrong directory |

Exits with code 1 if any errors are found — safe to use in CI.

Why This Exists

You've seen it: npm install fails with a wall of red text and the actual reason is buried three screens up. Sometimes it's the wrong Node version. Sometimes it's a lock file from a different package manager. Sometimes it's a permission issue that happened six months ago. This tool scans your project in two seconds and names the culprit.


More tools from Working Model → workingmodel.co · npm @workingmodel