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

@no-throw/oxlint-plugin

v0.2.0

Published

The oxlint adapter for no-throw. Contains no analysis.

Readme

@no-throw/oxlint-plugin

The oxlint adapter for no-throw. It turns findings from @no-throw/core into diagnostics and suggestions, and contains no analysis.

It ships the same two rules as the ESLint adapter, under the same names, saying the same words:

{
  "jsPlugins": ["@no-throw/oxlint-plugin"],
  "rules": {
    "nothrow/no-escaping-throw": "error",
    "nothrow/valid-mark": "error"
  }
}

The rules are type-aware and oxlint hands a JS plugin no type information, so the plugin reads your program itself: the tsconfig.json above each file that includes it — the nearest first, then the ones above — one program per config. A file no project includes is a diagnostic naming the config to fix, never a silent pass.

Two host-specific notes. The preset's third rule has an oxlint counterpart — enable typescript/no-floating-promises with --type-aware to cover the same float hygiene. And oxlint --fix never applies a bridge, exactly as eslint --fix never does; --fix-suggestions applies every offered bridge in bulk, which is accepting every bridge blind — the one choice the suggestion channel exists to leave with you.

The documentation is the root README — hosting in oxlint, what each rule holds you to, and why an offered bridge is never an autofix.