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

@sleepingasteroid/bluehop-git-hooks

v0.1.0

Published

One-command husky + lint-staged + commitlint (conventional commits) setup.

Readme

@sleepingasteroid/bluehop-git-hooks

Automatically lint, format, and check your commit messages every time you commit — set up with a single command.

What is this?

Git hooks are scripts that git runs automatically at certain moments — for example, right before a commit is created. They're great for catching problems before they ever land in your history, but wiring them up normally means installing and configuring three separate tools:

  • husky — installs the git hooks
  • lint-staged — runs linters/formatters on just the files you're committing
  • commitlint — checks your commit message follows a convention

This package bundles all three and sets them up for you with one command. The hooks call this package's own wrapper scripts, so everything resolves reliably under pnpm — you don't install husky, lint-staged, or commitlint yourself.

What you get

  • On every commit, your staged files are auto-fixed with ESLint and Prettier.
  • Bad commit messages are rejected — messages must follow Conventional Commits, e.g. feat(auth): add password reset.
  • It survives fresh clones — a prepare script reinstalls the hooks after pnpm install.

Install

pnpm add -D @sleepingasteroid/bluehop-git-hooks
npx bluehop-hooks-init

bluehop-hooks-init sets everything up (it's safe to re-run anytime):

  • initializes husky (creates .husky/)
  • writes .husky/pre-commit → runs lint-staged
  • writes .husky/commit-msg → validates the message against Conventional Commits
  • scaffolds a lint-staged.config.mjs you can customize
  • adds "prepare": "bluehop-hooks-init" to your package.json so hooks reinstall after a clone

The commit-message check is self-contained — it always enforces Conventional Commits and needs no commitlint.config file in your project.

Requirements: a git repo (run git init first) and eslint + prettier available in the project (they come with bluehop-eslint-config and bluehop-prettier-config).

What runs by default

  • pre-commit: ESLint --fix + Prettier --write on staged JS/TS files; Prettier on staged JSON/Markdown/CSS/YAML files.
  • commit-msg: rejects any message that isn't a Conventional Commit.

Customizing what runs on commit

Edit the lint-staged.config.mjs that was scaffolded into your project. It starts by re-exporting the shared defaults, so you only add what's different:

// lint-staged.config.mjs
import shared from '@sleepingasteroid/bluehop-git-hooks/lint-staged'

export default {
  ...shared,
  '*.rs': ['cargo fmt --'], // e.g. also format Rust files
}

Part of the bluehop toolkit — a set of shareable project configs.