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

@willbooster/wb

v13.4.2

Published

CLI tool for WillBooster projects

Readme

@willbooster/wb

wb offers a collection of reusable npm scripts, designed primarily for WillBooster Inc. but with potential utility for other projects as well.

Supported Platforms

wb does not support Windows. Use it on macOS, Linux, or another POSIX-compatible environment.

Usage

wb <command>

Commands:
  wb buildIfNeeded              Build code if changes are detected
  wb kill-port-if-non-ci        Kill the port specified by PORT environment
                                variable if non-CI.
  wb lint [files...]            Lint code
  wb optimizeForDockerBuild     Optimize configuration when building a Docker
                                image
  wb prisma                     Run prisma commands
  wb retry [command] [args...]  Retry the given command until it succeeds
  wb setup                      Setup development environment. .env files are
                                ignored.
  wb start [args..]             Start app
  wb test [targets...]          Test project. If you pass no arguments, it will
                                run all tests.
  wb test-on-ci                 Test project on CI with no options.
  wb typecheck                  Run type checking. .env files are ignored.
  wb tc                         Run type checking. .env files are ignored.

Options:
      --env               .env files to be loaded.                       [array]
      --cascade-env       Environment to load cascading .env files (e.g.,
                          `.env`, `.env.<environment>`, `.env.local` and
                          `.env.<environment>.local`). Preferred over
                          `cascade-node-env` and `auto-cascade-env`.    [string]
      --cascade-node-env  Same with --cascade-env=<NODE_ENV || "development">.
                          Preferred over `auto-cascade-env`.           [boolean]
      --auto-cascade-env  Same with --cascade-env=<WB_ENV || NODE_ENV ||
                          "development">.              [boolean] [default: true]
      --include-root-env  Include .env files in root directory if the project is
                          in a monorepo and --env option is not used.
                                                       [boolean] [default: true]
      --check-env         Check whether the keys of the loaded .env files are
                          same with the given .env file.
                                              [string] [default: ".env.example"]
  -v, --verbose           Whether to show verbose information          [boolean]
  -w, --working-dir       A working directory                           [string]
  -d, --dry-run, --dry    Whether to skip actual command execution     [boolean]
      --version           Show version number                          [boolean]
      --help              Show help                                    [boolean]