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

@riddance/env

v0.9.9

Published

Too much code slows you down, creates risks, increases maintainability burdens, confuses AI. So let's commit less of it.

Downloads

992

Readme

Code is a Liability

Too much code slows you down, creates risks, increases maintainability burdens, confuses AI. So let's commit less of it.

With just one dev dependency, you get

  • Testing with built-in mocking support
  • Strict type checking
  • Strict linting
  • Formatting
  • Spell checking
  • LLM rules
  • customized MCP server (coming soon)
  • Automatic npm install
  • IDE setup
  • git setup
  • Dev Container setup
  • all in a hot-reloading trigger-on-save setup

Using carefully curated and optimized well-established open source packages, so you don't have to commit and maintain all of that yourself. It's even opinionated, so you avoid wasting time bike-shedding.

Get Started

Simply run

$ npm init riddance

Drop a .ts file in the directory, run

$ npm start

Try adding a type error, a spelling error, or some bad formatting, and see it react. Try adding a dependency to package.json and see it install automatically. Drop a Mocha test file in a test directory and see it run the tests.