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

bool-cli

v0.2.5

Published

CLI tool for bool.com

Readme

bool-cli

CLI tool for managing projects on bool.com.

Installation

npm install -g bool-cli

This installs the bool command globally.

Setup

bool auth login      # Paste your API key from the bool.com web UI
bool auth status     # Verify connection

Your API key is saved to ~/.config/bool-cli/config.json. You can also set the BOOL_API_KEY environment variable.

Commands

Authentication

| Command | Description | |---|---| | bool auth login | Save API key | | bool auth status | Check auth + API health |

Ship It

The fastest way to get code live — no account or API key required:

bool shipit [directory]

Creates an anonymous Bool and uploads files in one step. On subsequent runs from the same directory, it updates the existing Bool automatically (tracked via .bool/config).

Options

| Option | Description | |---|---| | --slug <slug> | Update an existing anonymous Bool instead of creating a new one | | --name <name> | Bool name (defaults to config, then directory name) | | -m, --message <msg> | Commit message (used when updating) | | --base-url <url> | Base URL (or set BOOL_BASE_URL) |

Bools

| Command | Description | |---|---| | bool list [--limit <n>] | List Bools (default: 20) | | bool create <name> | Create a new Bool | | bool show [slug] | Show Bool details + latest version | | bool update [slug] [--name] [--description] [--visibility] | Update a Bool | | bool delete [slug] [-y] | Delete (with confirmation, skip with -y) | | bool open [slug] | Open editor URL in browser |

Aliases:

  • bool ls for bool list
  • bool get / bool info for bool show
  • bool rm for bool delete

Deprecated but still supported:

  • bool bools ... commands now print a deprecation warning and map to top-level commands.
  • bool bools visibility ... is deprecated; use bool update [slug] --visibility <value>.

Slug resolution: When [slug] is omitted, commands read it from the .bool/config file in the current directory. This file is created automatically by shipit, deploy, pull, and show (or info alias).

Versions & Deployment

| Command | Description | |---|---| | bool versions [slug] | List version history | | bool deploy [slug] [dir] | Deploy local files as a new version (creates Bool if needed) | | bool pull [slug] [dir] | Download files to a local directory |

Deploy options

bool deploy my-project ./src --message "Added dark mode" --exclude "*.test.js"
  • Auto-create: If no slug is provided and .bool/config doesn't exist, a new Bool is created automatically (named after the directory)
  • --message / -m — Commit message
  • --exclude — Exclude pattern (repeatable)
  • Binary files are automatically skipped
  • Respects .boolignore files (gitignore syntax)
  • Default excludes: .git, node_modules, __pycache__, .DS_Store, .bool
  • Live URL: Displayed in output after successful deployment

Pull options

bool pull my-project ./local-copy --version 3
  • --version — Specific version number (default: latest)

JSON output

All commands support --json for machine-readable output:

bool list --json
bool show my-project --json

Project Config

Running shipit, deploy, pull, or show creates a .bool/config file in the project directory. This JSON file stores slug and name so you can run commands without specifying the slug each time:

cd my-project
bool deploy              # slug read from .bool/config
bool show                # slug read from .bool/config
bool versions            # slug read from .bool/config

Add .bool/ to your .gitignore.

Project Structure

bool-cli/
  bin/
    bool.js              # Entry point
  src/
    commands/
      auth.js            # auth login, auth status
      bools.js           # top-level bool commands (+ deprecated bools wrappers)
      shipit.js          # shipit (anonymous create + deploy)
      versions.js        # versions, deploy, pull
    utils/
      api.js             # API client (fetch-based)
      config.js          # Global config + project-level .bool/config
      files.js           # File reading, .boolignore, binary detection
      output.js          # Output formatting (tables, colors, JSON)