JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • 0
  • Score
    100M100P100Q43915F
  • License ISC

A CLI tool for visualizing Claude Code usage metrics with byobu integration

Package Exports

  • ccusage-byobu
  • ccusage-byobu/lib/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (ccusage-byobu) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

ccusage-byobu

Installation

git clone git@github.com:adawalli/ccusage-byobu.git
cd ccusage-byobu
npm install

Development

This project uses Husky pre-commit hooks to maintain code quality. The hooks automatically run:

  • ESLint - Lints and auto-fixes JavaScript files
  • Prettier - Formats JavaScript and JSON files
  • Commitlint - Validates commit message format

Git Hooks

Pre-commit Hook

Runs lint-staged to check only staged files for:

  • ESLint linting with auto-fix
  • Prettier formatting

Commit Message Hook

Validates commit messages follow Conventional Commits format:

  • feat: add new feature
  • fix: resolve bug
  • docs: update documentation
  • style: format code
  • refactor: restructure code
  • test: add tests
  • chore: maintenance tasks

Bypassing Hooks (Emergency Use Only)

⚠️ Use with caution - Only bypass hooks when absolutely necessary

Skip All Hooks

git commit --no-verify -m "emergency fix"

Skip Specific Steps

# Skip pre-commit but allow commit-msg validation
HUSKY=0 git commit -m "feat: emergency feature"

When to Bypass

  • Hotfixes - Critical production issues requiring immediate deployment
  • WIP Commits - Work-in-progress commits in feature branches (consider using git stash instead)
  • Hook Failures - When hooks themselves have issues (rare)

After Bypassing

Always clean up bypassed commits:

  1. Fix any code quality issues
  2. Ensure tests pass
  3. Format and lint code properly
  4. Consider amending or squashing commits before merging