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

@crbroughton/eslint-plugin-failsafe

v0.1.0

Published

ESLint rules enforcing @crbroughton/failsafe usage patterns

Readme

@crbroughton/eslint-plugin-failsafe

ESLint rules enforcing @crbroughton/failsafe usage patterns — catching the library's own documented footguns before they ship.

Install

pnpm add -D @crbroughton/eslint-plugin-failsafe

Usage

Every rule is on by default via configs.recommended:

// eslint.config.js
import antfu from "@antfu/eslint-config"
import failsafe from "@crbroughton/eslint-plugin-failsafe"

export default antfu(
  { type: "lib" },
  {
    files: ["src/**/*.ts"],
    ...failsafe.configs.recommended,
  },
)

Two of the five rules are type-aware (require-match-on-tagged-error, no-unused-result) and need type-aware linting enabled for the matched files (see typescript-eslint's typed linting docs). For consumers who haven't set that up, use configs.recommendedUntyped instead — the same rules minus the ones that require type information.

Rules

| Rule | Type-aware | Description | | --- | --- | --- | | no-raw-throwing-call | No | Disallow direct calls to native APIs failsafe/try already wraps, unless routed through safe() or the matching tryX() | | require-match-on-tagged-error | Yes | Require a multi-tag .error union to be handled with match(), not used directly | | no-unused-result | Yes | Require a Result-producing call used as its own statement to be assigned to a variable | | no-async-thunk-in-safe | No | Disallow safe(async () => ...) — matches the sync overload, never awaits the rejection | | no-throw-in-gen-block | No | Disallow a raw throw inside a gen() block — escapes as a real exception instead of becoming an Err |

See each rule's doc for full details, examples, and known limitations.

License

MIT