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 🙏

© 2025 – Pkg Stats / Ryan Hefner

nodeinit

v4.1.14

Published

Creates a most frequent scaffold of your node.js project for the first commit.

Downloads

78

Readme

nodeinit

Creates a most frequent scaffold of your node.js project for the first commit.

Why ?

I was awefully insane about creating new node.js projects, creating new github repo, cloning, npm init, .gitignore, travis-ci config, git init ............

I was INSANE about answering questions from yeoman.

We might as well:

nodeinit https://github.com/kaelzhang/nodeinit.git # and done!

Installation

$ npm install -g nodeinit

Usage

$ nodeinit <repo-url> [--email <email>] [--npm_user <npm-user>]

nodeinit can not analysis your email and npm user name from the repo, so you must pass them to nodeinit for the first time you run the command.

After this, the configuration will be saved into ~/.nodeinit.

Also, you could edit the file as you wish.

~/.nodeinit

Usually, you can config your ~/.nodeinit file like this:

email = [email protected]

; will be saved as `package.author` in package.json
npm_user = kael

; if not specified, nodeinit will parse the user name from the clone URL.
user = kael