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/oxlint-plugin-result-kit

v0.1.1

Published

Oxlint (syntax-tier) port of must-use-result — a re-export of the shared rule-core rule.

Readme

@zireal/oxlint-plugin-result-kit

The Oxlint port of @zireal/result-kit's must-use-result rule — syntax tier. It shares the exact rule brain with the ESLint plugin, re-exported verbatim.

Install

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

Peer dependency: oxlint. Oxlint JS plugins are alpha as of early 2026.

Usage

Register the plugin in your Oxlint config and enable the rule (see the Oxlint JS-plugins guide for the current wiring):

// .oxlintrc.json
{
  "jsPlugins": ["@zireal/oxlint-plugin-result-kit"],
  "rules": {
    "@zireal/result-kit/must-use-result": "error"
  }
}

Rules

  • must-use-result — a Result-returning call whose value is dropped in statement position is flagged. Options: packageName (string, default "@zireal/result-kit").

Capability honesty (read this)

Oxlint cannot give a third-party rule type information, so this is the syntax tier, not the full rule. It recognises a Result call two ways:

  1. the callee is imported from @zireal/result-kit, or
  2. the callee is a locally-declared function whose return-type annotation textually names Result.

It cannot see two shapes — a call whose Result return is inferred (no annotation), or whose return type aliases Result behind another name. Measured recall is ~82% of dropped Results on a representative corpus; the two blind spots are unreachable without types.

For full-fidelity, type-aware enforcement (through wrappers, aliases, and unions), use @zireal/eslint-plugin-result-kit.

License

MIT © Ali Farooq