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

@genji-ball-team/style

v1.0.0

Published

The Genji Ball coding style: ESLint and Prettier config, the file-size check and the pre-commit hook

Readme

Genji-Ball-Team/.github

Team-wide files for every Genji-Ball-Team repo:

  • STYLE.md: the coding style for TypeScript, Rust and OverPy.
  • CONTRIBUTING.md: shown as the contributing guide in every repo of the org.
  • @genji-ball-team/style: the shared ESLint and Prettier config, the file-size check and the pre-commit hook, published to npm from this repo.

Using the package

npm install --save-dev @genji-ball-team/style eslint prettier typescript

package.json:

{
  "prettier": "@genji-ball-team/style/prettier",
  "scripts": {
    "prepare": "gb-hooks install",
    "lint": "prettier --check . && eslint . && gb-size"
  }
}

eslint.config.js at the repo root, next to the tsconfig.json:

import { styleConfig } from "@genji-ball-team/style/eslint";

export default styleConfig({ root: import.meta.dirname, ignores: ["dist/"] });
  • gb-size checks the tracked Rust and OverPy files against the size limit (ESLint max-lines covers TS and JS). In Rust, a file's #[cfg(test)] part counts against the test limit.
  • .size-exceptions at the repo root lists the files already over the limit, one path per line, each with its split issue in a # comment. Both ESLint and gb-size read it, and gb-size fails when a listed file is gone or under the limit, so the list only shrinks.
  • gb-hooks install writes the pre-commit hook (it leaves an existing hook of someone else's alone, and does nothing in CI). The hook runs Prettier, ESLint and gb-size on the staged files, each only if the repo has it. git commit --no-verify skips it once.
  • Line endings: add a .gitattributes with * text=auto eol=lf. Prettier wants LF, and without it a Windows checkout (CRLF) fails prettier --check.
  • Rust: copy rust/clippy.toml next to Cargo.toml, and paste rust/lints.toml into it.
  • OverPy (CE): only gb-size and the hook; leave out ESLint, Prettier and TypeScript.

Working on it

npm ci
npm run check   # typecheck (tsc on the JS), Prettier, ESLint, size check, node --test

The package is plain JavaScript with JSDoc types, so ESLint and Node load it without a build.

Make a release

  1. Bump version in package.json in its PR (a rule that fails more code is a major version).
  2. After the merge, tag the merge commit and push the tag: git tag v1.0.0 && git push origin v1.0.0. The Release workflow checks and publishes it to npm.
  3. Write the GitHub release notes by hand: gh release create v1.0.0 --notes-file <notes>. Say what changed and what repos must change.