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

create-package-javascript

v0.2.7

Published

Recklessly create npm packages left and right with this single command

Downloads

4

Readme

Usage

create-package-javascript was designed with npm init … approach in mind (learn more about npm init).

npm init package-javascript my-package
npm init package-javascript my-foo-package --in ./path/to/my-packages/foo

--in

By default, all the files are put to a new directory named after the package name:

cd ~
npm init package-javascript my-package
~/
  my-package/
    package.json # "name": "my-package"

This behavior can be overriden with --in option. For example, this command:

cd ~
npm init package-javascript my-foo-package --in ./path/to/my-packages/foo

… creates these files:

~/path/to/my-packages/
  foo/
    package.json # "name": "my-foo-package"

Different versions

By default, the create-package-javascript@latest is used. To use different version of create-package-javascript, consider this syntax: