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-ts

v0.4.3

Published

codelaw's TypeScript rules, from typescript-eslint; npm only (SR-RULE-PACKS)

Readme

@codelaw/rules-ts

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

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

Presets

| preset | rules | ported from | |---|---|---| | ts/recommended | 20 | typescript-eslint recommended 8.71.2 (not type-checked) — all 20 rules; the four core rules its eslint-recommended switches on are codelaw:js/typescript in @codelaw/rules-js | | ts/conventions | 1 | codelaw's starter catalogue: ts/type-only-imports — opt in | | ts/type-checked | 6 | typescript-eslint's type-checked rules, answered by the project's own TypeScript ≥ 7.1 (SR-TYPES); every rule is preview until TypeScript 7.1 is GA |

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 | |---|---| | ts/no-unused-expressions | x satisfies T; is a compile-time type test and is allowed |

Nothing from typescript-eslint's non-type-checked recommended is left out.

Type-checked rules

ts/type-checked holds the rules that need types, answered by your project's own TypeScript — 7.1 or later, the typescript package installed from the file's folder up to the project root — through a small Node helper inside codelaw (SR-TYPES). codelaw installs no TypeScript. Without Node or TypeScript ≥ 7.1 they are skipped, and the report says why; everything else runs. Every one is preview until TypeScript 7.1 is GA, and the report names the TypeScript version that answered.

# codelaw.toml
extends = ["codelaw:ts/recommended", "codelaw:ts/type-checked"]
preview = true

| rule | from typescript-eslint | |---|---| | ts/no-floating-promises | no-floating-promises | | ts/await-thenable | await-thenable | | ts/no-unsafe-call | no-unsafe-call | | ts/no-unsafe-member-access | no-unsafe-member-access | | ts/no-unsafe-return | no-unsafe-return | | ts/type-error | — TypeScript's own errors, as tsc reports them |

The rest of typescript-eslint's recommended-type-checked is not built yet (W-105). no-misused-promises' condition check is TypeScript's own error TS2801, which ts/type-error reports. A hook (codelaw hook) never loads a type program: it uses a warm one (codelaw daemon start) or skips the type rules with a note.