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

@nojaf/oxlint-plugin-annotate-non-primitives

v0.1.1

Published

Oxlint rule requiring an explicit type annotation whenever the type is not obvious from the initializer.

Readme

@nojaf/oxlint-plugin-annotate-non-primitives

An oxlint plugin with a single rule: write down the type whenever it isn't obvious from the initializer.

Inference is convenient while writing code and unhelpful while reading it. This rule keeps the shorthand where the type is already staring at you (literals, comparisons, casts) and asks for an annotation everywhere else.

Install

bun add -d @nojaf/oxlint-plugin-annotate-non-primitives
npm install --save-dev @nojaf/oxlint-plugin-annotate-non-primitives

Configure

Add the package to jsPlugins and switch the rule on in .oxlintrc.json:

{
  "jsPlugins": ["@nojaf/oxlint-plugin-annotate-non-primitives"],
  "rules": {
    "nojaf/annotate-non-primitives": "error"
  }
}

The rule lives under the nojaf namespace. To use a different one, give the plugin an alias:

{
  "jsPlugins": [
    {
      "name": "house-style",
      "specifier": "@nojaf/oxlint-plugin-annotate-non-primitives"
    }
  ],
  "rules": {
    "house-style/annotate-non-primitives": "error"
  }
}

What the rule does

Variable declarations

const and let declarations need an annotation unless the initializer makes the type obvious.

Allowed as-is:

const answer = 42;
const greeting = "hello";
const enabled = true;
const template = `hello ${greeting}`;
const remainder = answer % 60;
const padded = remainder < 10 ? "0" : "1";
const top = expr as Pixels;
const schema = z.object({ name: z.string() });

Reported:

const rect = el.getBoundingClientRect();
const acc = [];
const node = nodes[i]!;
const body = document.body;
const double = (value: number): number => value * 2;

Destructuring patterns (const { a } = obj) and declarations without an initializer (let x;) are skipped — the first has no single name to annotate, the second is already annotated or genuinely untyped.

Arrow function parameters

Every identifier parameter of an arrow function needs a type annotation:

items.map((value) => value.length); // reported
items.map((value: string) => value.length); // fine

Requirements

  • oxlint 1.x with JS plugins enabled (JS plugins are alpha and not subject to semver).
  • Node.js 18+ for the published build (plain ESM, no runtime dependencies).

Development

bun install
bun test        # runs oxlint over test/fixtures and asserts the diagnostics
bun run lint    # the plugin lints its own source
bun run typecheck
bun run build   # emits dist/

To inspect the AST oxlint hands to the rule:

echo 'const x = foo();' | bun run scripts/ast.ts

The oxc AST can differ from what you would expect from ESTree, so check the real node shape before matching on it.

License

MIT