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

init-npm-project

v3.0.0

Published

minimal setup for an npm project

Readme

init-npm-project

arrange a minimal setup for an npm project

Installation

This package is best consumed as a CLI command, so

npm install --global init-npm-project

Usage

init-npm-project [--name] [--description] [--author] [--no-github] [--no-mkdir]

By default, name, description and author name are asked before creation. If you like one-liners, you may provide them using the named args. GitHub credentials cannot be provided as args, you always have to type them.

console output

--name

The name of your next project.

--description

The description of you next project.

--author

Your name (and optionally email). This gets directly dumped in the package.json author field.

--no-mkdir

Do not create a dir but use an existent one. Be careful because the tool may overwrite existing files (package.json, README.md, .gitignore).

--no-github

If this flag is specified, nothing GitHub-related will be done. Otherwise, the tool will ask for your GitHub credentials (which are not stored in any way, you can check the code).

License

MIT