Skip to content
This repository has been archived by the owner before Nov 9, 2022. It is now read-only.


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Create a new node module with all the right stuff.

npm travis standard downloads


module-init is a command-line tool for generating a new node module.

The following list of files are created based on user input:

    • Automatically generates title, description, and some tasteful badges (version, build status, code style).
    • Auto-populates install, usage, contributing, and license sections with relevant info.
    • Options: Apache-2.0, BSD-3-Clause, CC0-1.0, ISC, MIT, UNLICENSED.
    • Optionally generates contributing guidelines based on boilerplate.
  • package.json
  • .travis.yml
    • Covers Node.js 4 and 6.
  • .gitignore
    • Ignores node_modules directory.
  • index.js
    • A blank module entry point file.
  • test/index.js
    • A boilerplate test file using tape.

Optionally runs git init and npm install in the new module directory.


npm install module-init -g



$ module-init --help
Usage: module-init [options]
    --dir, -d             specify module directory (default: cwd)
    --version, -v         show version information
    --force, -f           skip prompt and init with defaults
    --help, -h            show help


~ $ module-init -d new-project
? name: new-project
? version: 1.0.0
? description:
? keywords:
? license: ISC
? private: No
? Yes
? linter: standard
? git init: Yes
? npm install: Yes
Initialized empty Git repository in /Users/yourname/new-project/.git/
✓ .gitignore created
✓ .travis.yml created
✓ created
✓ created
✓ LICENSE created
✓ created
✓ package.json created
✓ index.js created
✓ test/index.js created
tape@4.0.3 node_modules/tape
tap-spec@4.0.2 node_modules/tap-spec
standard@5.0.2 node_modules/standard
✓ new-project initialized

Node API

module-init can also be required as a regular node module.

Configuration properties from other sources (.gitconfig, current working directory) will not be automatically used as defaults in this mode. All required properties need to be passed in explicitly.

var moduleInit = require('module-init')

var options = {
  pkgName: 'cool-package',          // required
  pkgVersion: '1.0.0',              // required
  usrName: 'Your Name',             // required
  usrEmail: '',       // required
  usrGithub: 'githubUsername'       // required
  pkgDescription: 'description',    // optional
  pkgKeywords: 'one, two, three',   // optional
  pkgContributing: true,            // optional, default: true
  pkgLinter: 'standard',            // optional, default: standard
  pkgLicense: 'ISC',                // optional, default: ISC
  private: true,                    // optional, default: false (omitted if false)
  dir: 'project-directory'          // optional: default: cwd

  .on('create', function (filename) {
    console.log(`${filename} created`)
    // file created
  .on('warn', function (message) {
    console.log(`warning: ${message}`)
    // something weird but non-critical happened
  .on('err', function (err) {
    // something went horribly wrong! stop everything!
  .on('done', function (result) {
    console.log(result) // object containing module metadata
    // done!
  .run() // run the thing

moduleInit returns an event emitter that emits create, warn, err, and done.

moduleInit.on(string, function) works as demonstrated in the example above. runs the initialization process. It also calls moduleInit.validate() internally before proceeding and will emit an err event if required options are missing. Event listeners need to be set before is called.

moduleInit.validate() returns an array of missing required options. It returns an empty array if everything's fine. This method is really just for internal use, but is exposed for testing and convenience.

Take a look at bin/cli.js to see how the API is being used by the CLI.


Contributions welcome! Please read the contributing guidelines before getting started.


module-init is only possible due to the excellent work of the following collaborators:


See Also