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 🙏

© 2024 – Pkg Stats / Ryan Hefner

starter-kit

v2.2.0

Published

A quick command-line utility for NodeJS that helps quickly spin up new projects.

Downloads

29

Readme

StarterKit

A command-line utility for Node that gives quick access to starter-kits that help you spin up a project easily. Designed for teams that desire consistency but require flexibility from project to project.

Install

npm install starter-kit -g

Basic Usage

mkdir your_directory
cd your_directory
starterkit use starter-kit

As a general rule, every Starterkit has a ./bin/bootstrap file that sets up the requirements of that Starterkit, and a ./bin/dev-start file that begins what development process is needed.

Starter Kits

Additional Libraries

You can install any library available on Bower or NPM through the use command as well! Simply add --bower and/or --npm as an option on your command.

Examples:

starterkit use frontend-starter --bower jquery,bourbon,neat
starterkit use react-starter --bower bourbon --npm jquery,radium

Building a Starter Kit

Want to build a starter kit? Awesome! It's really rather simple. Just follow these principles, build your starter kit, and then submit a pull-request with a link to your wonderful starter kit.

Starter Kit Principles

  1. Only the bare necessities. People shouldn't feel the need to delete anything in a starter kit.
  2. ./bin/bootstrap is the only way to setup. The starterkit cli calls ./bin/bootstrap when installing starter kits, so chances are the setup will just fail. The idea is that a user should not have to run a single line of code to get their project ready to go after using the starter kit.