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 🙏

© 2024 – Pkg Stats / Ryan Hefner

crufty

v1.0.4

Published

A CLI tool to check for files exceeding line count thresholds, because we all accumulate cruft over time.

Downloads

319

Readme

crufty

Because we all accumulate cruft over time.

A command-line tool to check for files that exceed specified line count thresholds in your codebase. Perfect for maintaining code quality and identifying potentially complex files that might need refactoring.

Installation

npm install -D crufty
# or
pnpm add -D crufty
# or
yarn add -D crufty

Usage

crufty ./**.{ts,js,jsx,astro} [options]

By default, crufty will check all files in the current directory against a threshold of 100 lines. You can specify file patterns or paths to check specific files.

Examples

# Check all files in current directory
crufty

# Check specific files or patterns
crufty src/**/*.ts src/**/*.js

# Set custom line threshold
crufty --threshold 200

# Warn instead of throwing error
crufty --warn

# Ignore specific patterns
crufty --ignore "*.test.ts,*.spec.js"

Options

  • -t, --threshold <number>: Line count threshold (default: 100)
  • -w, --warn: Warn instead of throwing error (default: false)
  • --no-gitignore: Disable gitignore patterns
  • -s, --silent: Suppress all output except errors
  • -i, --ignore <patterns>: Additional patterns to ignore (comma-separated)
  • -v, --version: Output the version number
  • -h, --help: Display help for command

Using with lint-staged and husky

You can use crufty as part of your pre-commit hooks to prevent committing files that exceed your line count threshold. Here's how to set it up:

  1. Install the required dependencies:
npm install -D lint-staged husky
# or
pnpm add -D lint-staged husky
# or
yarn add -D lint-staged husky
  1. Initialize husky:
npx husky
  1. Add the following to your package.json:
{
  "scripts": {
    "prepare": "husky install"
  },
  "lint-staged": {
    "*.{js,jsx,ts,tsx,astro}": ["crufty"]
  }
}
  1. Add the pre-commit hook:
npx husky add .husky/pre-commit "npx lint-staged"

Now crufty will run on all staged files before each commit, preventing commits that would introduce files exceeding your line count threshold.