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-is-this-failing-in-prod

v1.0.0

Published

Tells you in plain English why your app works locally but breaks in production.

Readme

@workingmodel/why-is-this-failing-in-prod

Tells you in plain English why your app works locally but breaks in production. Developed by Working Model.

npm version npm downloads license

why-is-this-failing-in-prod

Scanning: /Users/you/my-app
Node: v20.11.0

✖ [Environment] 2 env var(s) in .env.example have no local value: DATABASE_URL, JWT_SECRET
  → These are likely missing in prod too. Add them to your deployment environment.

⚠ [Build Output] dist/ exists locally but is in .gitignore — prod won't have it unless built in CI.
  → Make sure your CI/CD pipeline runs `npm run build` before starting the app.

✖ [Start Script] "start" script uses a TypeScript runner (tsx src/index.ts)
  → Build first, then start with node. Change to "start": "node dist/index.js"

Summary: 2 errors, 1 warning
Fix the errors above before deploying.

Install

npx @workingmodel/why-is-this-failing-in-prod

Or install globally:

npm install -g @workingmodel/why-is-this-failing-in-prod

Usage

Run in your project root:

why-is-this-failing-in-prod

Or point it at a specific directory:

why-is-this-failing-in-prod /path/to/my-app

Exits with code 1 if errors are found — pipe-friendly for CI.

What It Checks

| Check | What it catches | |-------|----------------| | Environment vars | Keys in .env.example missing from your local .env — likely missing in prod too | | Node version | Local Node doesn't satisfy your own engines.node range | | Build output | main points to dist/ but dist/ doesn't exist or is gitignored | | Start script | Missing start script, or start uses ts-node/tsx/nodemon in prod | | Local references | Hardcoded localhost addresses in npm scripts | | Platform fields | os or cpu fields that reject the current environment |

Why This Exists

You pushed. It deployed. It's broken. Your laptop is fine. The server is not. You've been staring at logs for forty minutes and the answer is a missing env var that was never in the deployment config because nobody wrote it down.

This tool is the checklist you should have run before pushing.


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