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

eslint-plugin-checked-error

v1.0.1

Published

ESLint rules for explicit error handling via return values

Readme

eslint-plugin-checked-error

Strict handling for functions that may return Error.

This plugin enforces a simple but important rule:

If a function may return an Error, you must not ignore its result.

Designed for TypeScript projects using ESLint v9 flat config and type-aware rules.


Installation

npm install --save-dev eslint eslint-plugin-checked-error typescript typescript-eslint

This plugin requires:

  • ESLint v9+
  • TypeScript
  • typescript-eslint (type-aware config)

Usage (Flat Config)

// eslint.config.mjs
import tseslint from 'typescript-eslint';
import tsParser from '@typescript-eslint/parser';
import checkedError from "eslint-plugin-checked-error";

export default [
  ...checkedError.configs.recommended,

  {
    languageOptions: {
      parser: tsParser,
      parserOptions: {
        project: true,
        tsconfigRootDir: import.meta.dirname,
      },
    },
  },
  plugins: {
    '@typescript-eslint': tseslint.plugin,
    'checked-error': checkedError,
  },
];

Included Configs

checked-error/configs/recommended

Enables:

  • checked-error/no-ignored-error-result
  • no-unused-vars
  • @typescript-eslint/no-unnecessary-condition
  • @typescript-eslint/strict-boolean-expressions
  • @typescript-eslint/only-throw-error

Rules

no-ignored-error-result

Disallows ignoring the result of a function call if its return type may include Error.

❌ Incorrect

function mayReturnError(): Error | true {
  return Math.random() > 0.5 ? new Error("fail") : true;
}

mayReturnError(); // ❌ result ignored
await mayReturnError(); // ❌ result ignored

✅ Correct

return mayReturnError();
throw mayReturnError();
const result = mayReturnError();
if (result instanceof Error) throw result;

What This Rule Does Not Do

This rule intentionally focuses on a single concern:

  • It only detects standalone calls whose result may be Error
  • It does not enforce how the error must be handled
  • It does not check unused variables
  • It does not validate boolean misuse

Those concerns are expected to be handled by:

  • no-unused-vars
  • @typescript-eslint/strict-boolean-expressions
  • @typescript-eslint/no-unnecessary-condition
  • @typescript-eslint/only-throw-error

Why?

Returning Error instead of throwing is sometimes used in:

  • FP-style code
  • effect systems
  • explicit error modeling
  • legacy migration scenarios

But silently ignoring such values creates subtle bugs.

This plugin ensures those values are never accidentally discarded.


Contributing

Issues and pull requests are welcome.


License

MIT