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

@rustwrap/eslint

v1.0.5

Published

A drop-in ESLint replacement (CLI + Node API) backed by the Rust-based oxlint for very fast linting. Honors .eslintrc(.json/.js/.yml), package.json#eslintConfig, flat eslint.config.js, and .eslintignore.

Readme

@rustwrap/eslint

A drop-in ESLint replacement (CLI + Node API) backed by the Rust-based oxlint for very fast linting. Honors your existing ESLint config and ignore files — point your eslint dependency at @rustwrap/eslint and lint ~50–80× faster.

Measured (representative PCF control)

| | ESLint | @rustwrap/eslint | |---|---|---| | src/**/*.{ts,tsx} (~50 files) | 38.0 s, 101 warnings | 0.48 s, 89 warnings |

(The small warning delta is the handful of ESLint rules oxlint doesn't yet implement — see Limitations. @rustwrap/eslint covers the large majority of correctness/style/TS/React rules.)

Use as an ESLint override

{
  "overrides": { "eslint": "npm:@rustwrap/eslint@^1" },
  "devDependencies": { "eslint": "npm:@rustwrap/eslint@^1" }
}

No script changes needed — eslint …, pcf-scripts lint, and tools using the ESLint Node API keep working. @rustwrap/eslint ships the eslint bin.

Requirements

Node.js ^20.19.0 || ^22.13.0 || >=24 (enforced via the package's engines field).

This is not an arbitrary floor — it is the exact intersection of the engine requirements of the Rust toolchain this package is built on:

| Dependency | Requires | Why | |---|---|---| | oxlint (+ native binding) | ^20.19.0 \|\| >=22.12.0 | The N-API/V8 features the Rust binary uses were backported into each LTS line at Node 20.19.0 and 22.12.0. | | eslint-scope | ^20.19.0 \|\| ^22.13.0 \|\| >=24 | Follows ESLint's policy: active LTS lines only, skipping odd non-LTS majors (21.x, 23.x). |

Taking the strictest clause on each line yields the declared range. Reading it:

  • ^20.19.0 → the Node 20 LTS line, from patch .19 up (>=20.19.0 <21). Earlier 20.x patches lack the backported native feature.
  • ^22.13.0 → the Node 22 LTS line, from patch .13 up (>=22.13.0 <23). Note this is one patch higher than oxlint's own 22.12.0 floor, because eslint-scope requires 22.13.0.
  • >=24Node 24+ (the next even LTS line and beyond).
  • Excluded: Node ≤16 (EOL), 18.x, 21.x, 22.0–22.12, and 23.x — none satisfy every dependency.

Node 16 / 18 are not supported. oxlint 1.x and Rolldown 1.x dropped them; the native Rust binaries will not run there. The engines field makes this an immediate, named EBADENGINE warning at install (or a hard failure under engine-strict=true/CI) instead of a cryptic deep crash inside the native module.

What it honors (config & ignore)

  • Legacy eslintrc: .eslintrc.json, .eslintrc, .eslintrc.js, .eslintrc.cjs, .eslintrc.yaml/.yml, and package.json#eslintConfig. Auto-discovered up the directory tree; --config/-c and --no-eslintrc respected.
  • Flat config: eslint.config.js/.mjs/.cjs (best-effort: rules, plugins, ignores).
  • extends — local file extends are merged; npm shareable configs (eslint:recommended, plugin:@typescript-eslint/recommended, plugin:react/recommended, airbnb, …) are mapped to the corresponding oxlint plugins.
  • plugins — mapped to oxlint plugin ids (@typescript-eslint→typescript, react/react-hooks →react, import, unicorn, jsx-a11y, jest, vitest, promise, n/node, jsdoc, vue, @next/next→nextjs).
  • rules — passed through with severities (off/warn/error/numeric/array). Rules oxlint doesn't implement are dropped automatically (it would otherwise reject the config).
  • env, globals, settings, overrides, ignorePatterns — translated (incl. normalizing settings.react.version: "detect" to a concrete version).
  • parser / parserOptions — TS/JSX is auto-detected by extension. parserOptions.project is honored for tsconfig resolution: oxlint auto-discovers the nearest tsconfig.json per file, and if your config points project at a non-standard tsconfig (e.g. tsconfig.eslint.json) it's passed through via --tsconfig. An explicit --tsconfig <file> CLI flag (and tsconfig Node API option) overrides discovery.
  • .eslintignore + --ignore-path + --ignore-pattern + --no-ignore.

CLI

ESLint-compatible flags: file/dir/glob args (incl. src/**/*.{ts,tsx} brace expansion — @rustwrap/eslint expands globs since oxlint doesn't), --fix, --quiet, --max-warnings <n>, -c/--config, --no-eslintrc, --ext, -f/--format <stylish|json|compact|unix|summary>, -o/--output-file, --ignore-path, --ignore-pattern, --no-ignore, --tsconfig <file>, --color/--no-color, --stdin/--stdin-filename. Other ESLint flags are accepted and ignored for drop-in tolerance.

Exit codes match ESLint: 0 clean (or warnings under threshold), 1 lint errors or --max-warnings exceeded, 2 fatal.

Node API

const { ESLint } = require("eslint"); // -> @rustwrap/eslint
const eslint = new ESLint({ cwd, fix });
const results = await eslint.lintFiles(["src/**/*.{ts,tsx}"]);
const formatter = await eslint.loadFormatter("stylish");
console.log(formatter.format(results));
await ESLint.outputFixes(results);

Implemented: ESLint (lintFiles, lintText, loadFormatter, calculateConfigForFile, isPathIgnored, static outputFixes/getErrorResults/version), legacy CLIEngine (executeOnFiles/executeOnText/getFormatter), Linter (verify/verifyAndFix), and loadESLint. Results use the ESLint LintResult shape (messages[] with ruleId/severity/line/column, errorCount/warningCount, …).

Engine & dependencies

  • Engine: oxlint (Rust/Oxc) — does the actual linting.
  • Compat layer: fast-glob (glob/brace expansion), js-yaml (YAML eslintrc).

Limitations

  • Rule coverage = oxlint's. ESLint rules oxlint doesn't implement (e.g. @typescript-eslint/naming-convention, @typescript-eslint/interface-name-prefix, react/prop-types, react/no-deprecated, react/display-name, react/self-closing-comp) are silently dropped, so a few project warnings won't be reported. Type-aware rules requiring full type information are not supported.
  • --fix applies oxlint's fixers (a subset of ESLint's).
  • Custom in-repo rules / --rulesdir / arbitrary ESLint plugins that aren't reimplemented in oxlint don't run.
  • Formatters cover stylish (default), json, compact, unix, summary. Other named formatters fall back to stylish.
  • Lints JS/TS/JSX only; .json/.scss/.md globs (which some configs include for other ESLint plugins) are matched but skipped.