create-package-javascript

parzh
js
create-package-javascript JS library on GitHub create-package-javascript JS library on npm Download create-package-javascript JS library

Recklessly create npm packages left and right with this single command

Version 0.2.7 License MIT
create-package-javascript has no homepage
create-package-javascript JS library on GitHub
create-package-javascript JS library on npm
Download create-package-javascript JS library

npm init package-javascript <name>

Recklessly create npm packages left and right with this single command ☝

Usage

npm init package-javascript <name> [--in <path>]

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:

npm init package-javascript@<version> <…options>