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

nodehub

v0.1.0

Published

jaubourg's simple node/github project init.

Downloads

30

Readme

NPM Build Status Coverage Status Dependency Status devDependency Status gratipay

nodehub

jaubourg's simple node/github project init.

Install

npm -g install nodehub

Usage

nodehub <project_name> [ "<project_short_description>" ] [ +bin ] [ +global ]

Where:

  • +bin indicates the package provides a command line script
  • +global indicates the package should be installed globally

In a Nutshell

nodehub superpack will:

  1. check for your git username using the git command (in my case jaubourg)
  2. get your info from GitHub (email, web page)
  3. create a subdirectory called superpack.
  4. create configuration for JSCS, JSHint and Travis CI
  5. add the text of the MIT license with proper copyright
  6. create a properly filled package.json file
  7. create a skeleton README.md with nice badges
  8. create a lib subdirectory with a main js file named after the project
  9. create a bin subdirectory if the +bin flag has been used
  10. create a Gruntfile that will export source coverage reports to Coveralls when executed on Travis CI
  11. Initialize git and point it to https://[email protected]/jaubourg/superpack.git
  12. NPM-install the dev dependencies

You just have to code from there!

Configuration on your end

  1. Create the corresponding repository on GitHub
  2. Add it to Travis CI
  3. Add it to Coveralls

Then push!

License

Copyright (c) 2015 Julian Aubourg

Licensed under the MIT license.