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

0-60

v2.1.0

Published

clone a skeleton repo and set up CI build as fast as possible

Readme

0-60

CircleCI Coverage Status semantic-release Commitizen friendly npm version

This is my script for creating an npm package from a skeleton project and setting up the CI build as fast as possible. Once you've used this you'll never want to go back to setting up all of that stuff manually.

Installation

yarn global add 0-60

Or if you want you can run it with npx:

npx 0-60

CLI

Cloning a skeleton repository

0-60 clone <REPO URL>[#<BRANCH>]

0-60 will prompt you for the new package name, organization, etc:

$ 0-60 clone https://github.com/jedwards1211/es2015-library-skeleton.git
? Destination directory: cool-project
Cloning into 'cool-project'...
remote: Enumerating objects: 182, done.
remote: Counting objects: 100% (182/182), done.
remote: Compressing objects: 100% (41/41), done.
remote: Total 1078 (delta 162), reused 150 (delta 140), pack-reused 896
Receiving objects: 100% (1078/1078), 586.17 KiB | 2.78 MiB/s, done.
Resolving deltas: 100% (724/724), done.
? Package name: cool-project
? Package description: made with 0-60!
? Package author: Andy Edwards
? Package keywords: foo,bar
? GitHub organization: jedwards1211
? GitHub repo: cool-project
Installing dependencies...
yarn install v1.13.0
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
✨  Done in 9.17s.
Ready to go!

Pick from preset list of skeleton repos

You don't have to type the repository URL every time. Instead you can configure a preset list of repositories to pick from by adding them to ~/.0-60.json. Then just run 0-60 without arguments, and outside of a repo directory. 0-60 will prompt you to select which skeleton you want from this list.

Example ~/.0-60.json:

{
  "skeletons": [
    "jedwards1211/es2015-library-skeleton",
    "jedwards1211/react-library-skeleton",
    "jedwards1211/react-karma-library-skeleton",
    "jedwards1211/untranspiled-js-library-skeleton",
    "jedwards1211/typescript-library-skeleton",
    "jedwards1211/typescript-library-skeleton#pnpm"
  ]
}
$ 0-60
? Skeleton repo: (Use arrow keys)
❯ jedwards1211/es2015-library-skeleton
  jedwards1211/react-library-skeleton
  jedwards1211/react-karma-library-skeleton
  jedwards1211/untranspiled-js-library-skeleton
  jedwards1211/typescript-library-skeleton
  jedwards1211/typescript-library-skeleton#pnpm

Preparing for CI build

Running 0-60 inside in your repo directory will:

  • Create the repository on GitHub
  • enable Travis CI (if .travis.yml is present)

Bringing in changes to the skeleton

Just run git pull skeleton master (0-60 keeps the skeleton repository URL in the skeleton remote). I recommend using the CLI in my fork of merge-package.json to automatically fix merge conflicts in package.json. (Install with npm i -g jedwards1211/merge-package.json#cli and then just run merge-package.json in the project directory after pulling.)