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

@cdbx/cli

v1.7.1

Published

CLI for @cdbx projects

Downloads

48

Readme

@cdbx/tools

Commitizen friendly

Global Installation

You can install these tools globally.

npm i -g .

Then access them globally from anywhere.

# Serve dev server from ./src folder
jsdevserver

# Run JS unit tests in ./src folder
jstester

# Convert ESNext in ./src to ES5 in ./dist
jsbuilder

# Preview the next release
jsreleaser

# Create the next release
jsreleaser --force

Project Installation

Or you can install them into your project.

npm i @cdbx/tools --save

Then setup your package.json to use these tools.

"scripts": {
  "serve": "jsdevserver",
  "test": "jstester",
  "build": "jsbuilder",
  "release": "jsreleaser"
}

Utilities

jsdevserver

Run a simple dev server without installing a bunch of crap into your repository or screwing with a dozen different configs.

See the jsdevserver readme for more information.

jstester

Execute unit tests on ESNext code without installing a bunch of crap into your repository or screwing with a dozen different configs.

See the jstester readme for more information.

jsbuilder

Transpile ESNext modules into ES5 without installing a bunch of crap into your repository or screwing with a dozen different configs.

See the jsbuilder readme for more information.

jsreleaser

Release modules in a sane manner without installing a bunch of crap into your repository or screwing with a dozen different configs.

See the jsreleaser readme for more information.

Development

Building

Rebuild all Docker images for all tools.

npm run build

Push to Registry

Push Docker images to Gitlab.

npm run push