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

@zgeoff/oxlint-config

v0.0.4

Published

Shareable oxlint config: strict categories, house-style rules, and a custom JS plugin

Readme

@zgeoff/oxlint-config

Shareable oxlint config: every category at error, restriction-rule cherry-picks, comment-style enforcement via @stylistic, and a bundled JS plugin (zgeoff/* rules) banning shapes no native oxlint rule can express — top-level arrows, nested function declarations, bare named exports, destructured and inline-typed parameters, ternary and await arguments, awaits hidden inside a control-flow condition or a &&/||/?? chain, and single-line /** … */ blocks (auto-fixed to multi-line; inline @type/@lends casts exempt).

Usage

bun add -d @zgeoff/oxlint-config oxlint @stylistic/eslint-plugin

Extend it from .oxlintrc.jsonextends resolves file paths only, so point at the file inside node_modules:

{
  "extends": ["./node_modules/@zgeoff/oxlint-config/oxlintrc.json"],
  // ignorePatterns don't propagate through extends — each consumer declares
  // its own (oxlint also honors .gitignore)
  "ignorePatterns": ["**/node_modules/**", "**/dist/**", "**/*.json"],
}

Or import the config object in oxlint.config.ts:

import config from '@zgeoff/oxlint-config';

The plugin is addressable on its own at @zgeoff/oxlint-config/plugin for configs that want the zgeoff/* rules without the rest.

Notes

  • The config enables the typescript, unicorn, oxc, import, and promise plugins and loads @stylistic/eslint-plugin through jsPlugins. oxlint resolves jsPlugins specifiers from the project root, not from the config file that names them — so @stylistic/eslint-plugin must be a direct dependency of the consuming project. Hoisting package managers (bun's default linker, npm) resolve it transitively anyway, but isolated layouts (pnpm, bun install --linker isolated) fail with Cannot find module '@stylistic/eslint-plugin' unless it's installed directly.
  • Type-aware rules activate under oxlint --type-aware (requires oxlint-tsgolint); the config works without it.