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

@zireal/eslint-plugin-result-kit

v0.1.1

Published

ESLint rules enforcing @zireal/result-kit's must-use-result vocabulary — the full-fidelity host.

Readme

@zireal/eslint-plugin-result-kit

Type-aware ESLint rules that enforce @zireal/result-kit's Result contract — the full-fidelity host of the must-use-result vocabulary. Closes the gap between Result in TypeScript and in Rust: a Result you produce but never handle should be an error, the way #[must_use] makes it one.

Install

pnpm add -D @zireal/eslint-plugin-result-kit

Peer dependencies (you almost certainly already have these): eslint >= 9, typescript >= 5, and @typescript-eslint/parser for type-aware linting.

Usage (flat config)

These rules are type-aware, so they need the TypeScript parser with type information enabled — exactly like any @typescript-eslint type-aware rule.

// eslint.config.js
import tseslint from "typescript-eslint";
import resultKit from "@zireal/eslint-plugin-result-kit";

export default tseslint.config({
  files: ["**/*.ts", "**/*.tsx"],
  languageOptions: {
    parser: tseslint.parser,
    parserOptions: { projectService: true }, // or: project: "./tsconfig.json"
  },
  plugins: { "@zireal/result-kit": resultKit },
  rules: {
    "@zireal/result-kit/must-use-result": "error",
    "@zireal/result-kit/no-throw-in-result-fn": "error",
  },
});

Or spread the bundled recommended config and add the type-aware parser options:

import tseslint from "typescript-eslint";
import resultKit from "@zireal/eslint-plugin-result-kit";

export default tseslint.config(
  resultKit.configs.recommended,
  { languageOptions: { parser: tseslint.parser, parserOptions: { projectService: true } } },
);

Rules

| Rule | Description | Fixable | |---|---|---| | must-use-result | A Result-returning expression whose value is dropped is an error. | ✅ (void) | | no-throw-in-result-fn | A function declared to return a Result should not throw. | — |

How detection works

Result is identified structurally (spec §2: { ok: true, value } | { ok: false, error }), never by where it was imported from — so a consumer's local type MyResult = Result<…> alias and a hand-rolled { ok, value } are both caught. must-use-result resolves the type through wrappers, aliases, and unions; carves out any (no false positives); and defers Promise<Result> to no-floating-promises. "Consumed" is emergent from the types — a terminal like unwrapOr / match returns a non-Result, so dropping it is fine; a transform like map / andThen returns another Result, so dropping it is flagged.

Related

License

MIT © Ali Farooq