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

@codelaw/rules-node

v0.4.3

Published

codelaw's Node.js rules, from eslint-plugin-n; npm only (SR-RULE-PACKS)

Readme

@codelaw/rules-node

codelaw's Node.js rules — one of codelaw's first-party rule packs (SR-RULE-PACKS). It ships on npm only, as @codelaw/rules-node; PyPI has no copy (L6 decision 11).

# codelaw.toml
extends = ["codelaw:js/recommended", "codelaw:node/recommended"]
preview = true   # every rule is `preview` until a corpus run promotes it

Presets

| preset | rules | ported from | |---|---|---| | node/recommended | 10 | eslint-plugin-n 18.5.0 recommended-module — 10 of its 14 rules: the 3 that need no package.json, node/hashbang, which reads the nearest package.json's bin, and the 6 import rules, which run on the project graph |

Every rule is reimplemented, not vendored: the matchers, messages and docs are written fresh, and each rule's ported_from: names the source rule.

How the ports differ

Every rule matches its source's documented behaviour on the source's own examples. Where codelaw differs, the rule's ## Differences from the source section says so. The larger ones:

| rule | difference | |---|---| | node/no-deprecated-api | the APIs come from the pack's node/deprecated-api table; the supported Node.js version is not read | | node/no-missing-import, node/no-missing-require | scope: project rules on the project graph, which never reads node_modules: only the project's own paths are judged (relative, absolute, tsconfig paths), and only extensionless or JavaScript/TypeScript ones; a package name is not looked up | | node/no-extraneous-import, node/no-extraneous-require | the nearest package.json only; a type-only import is satisfied by its @types/ package | | node/no-unpublished-import, node/no-unpublished-require | only in a package that is not private and lists files; .npmignore and the convertPath option are not read, so source files that build into files are not judged | | node/hashbang | JavaScript and JSX only (no convertPath for TypeScript sources); suggest, since removing a hashbang can stop a script that is run directly |

Not ported, and why

| rule | why | |---|---| | node/no-unsupported-features/es-builtins, /es-syntax, /node-builtins | need the project's Node.js version from package.json and per-version feature tables | | node/process-exit-as-throw | reports nothing; it only changes ESLint's code-path analysis |

Data

data/node/deprecated-api.json — Node.js APIs the Node.js documentation deprecates, with their replacements, written for this pack.