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

force-exit-zero

v0.1.0

Published

Force a command to exit with code 0 (success), regardless of the result. Perfect for CI pipelines.

Downloads

2

Readme

force-exit-zero

Force a command to exit with code 0 (success).

The Problem: Your CI fails because a linter found a warning, or a non-critical script returned exit code 1. You try adding || true but it doesn't work consistently across Windows/Linux shells.

The Solution: force-exit-zero runs your command, streams the output (colors preserved), and always reports success to the OS.

Install

npm install force-exit-zero

Usage

In package.json scripts

{
  "scripts": {
    "lint": "eslint .",
    "lint:ci": "force-exit-zero npm run lint"
  }
}

In GitHub Actions / CI

steps:
  - run: npx force-exit-zero npm run test:flaky

CLI

$ force-exit-zero ls --unknown-flag
ls: unrecognized option '--unknown-flag'
# (The command failed, but the process exited with 0)

Why not || true?

  • || true doesn't work in standard Windows cmd.exe.
  • || true can be confusing in complex npm run chains.
  • force-exit-zero is explicit: you are intentionally suppressing the failure.

License

MIT

{ github.com/mgks }

Website Badge Sponsor Badge