generate-project

Scaffold out complete code projects from the command line, or use this generator as a plugin in other generators to provide baseline functionality.

generate-project

Table of Contents

• What is "Generate"?
• Getting started
  • Install
  • Usage
  • Help
• Tasks
  • default
  • files
  • index
  • dotfiles
  • rootfiles
  • project
  • gulp
  • base
  • minimal
  • generator
  • helper
• Generated files
  • default
  • files
  • index
  • dotfiles
  • rootfiles
  • project
  • gulp
  • base
  • minimal
  • generator
  • helper
• Next steps
  • Running unit tests
  • Publishing your project
• About
  • Related projects
  • Community
  • Contributing
  • Running tests
  • Author
  • License

(TOC generated by verb using markdown-toc)

What is "Generate"?

Generate is a command line tool and developer framework for scaffolding out new GitHub projects using generators and tasks.

Answers to prompts and the user's environment can be used to determine the templates, directories, files and contents to build. Support for gulp, base and assemble plugins, and much more.

For more information:

• Visit the generate project
• Visit the generate documentation
• Find generators on npm (help us author generators)

Getting started

Install

Installing the CLI

To run the project generator from the command line, you'll need to install Generate globally first. You can do that now with the following command:

$ npm install --global generate

This adds the gen command to your system path, allowing it to be run from any directory.

Install generate-project

Install this module with the following command:

$ npm install --global generate-project

Usage

Run this generator's default task with the following command:

$ gen project

What will happen?

Running $ gen project will run the generator's default task, which will:

• prompt you for any information that's missing
• render templates using your answers
• generate the resulting files to the current working directory.

Conflict detection

In the case that a file already exists on the file system, you will be prompted for feedback before overwrite any files.

You can set the destination to a new directory if you want to avoid the prompts, or avoid accidentally overwriting files with unintentional answers.

What you should see in the terminal

If completed successfully, you should see both starting and finished events in the terminal, like the following:

[00:44:21] starting ...
...
[00:44:22] finished ✔

If you do not see one or both of those events, please let us know about it.

Help

To see a general help menu and available commands for Generate's CLI, run:

$ gen help

Tasks

All available tasks.

default

Generates the necessary files for a basic node.js project.

Example

$ gen project

files

Runs the default task on all registered micro-generators.

Example

$ gen project:files

index

Generate a basic index.js file. This task is used for composition with other tasks.

Example

$ gen project:index

dotfiles

Generate the dotfiles from registered micro-generators .

Example

$ gen project:dotfiles

rootfiles

Generate the main project files from registered micro-generators: contributing.md, LICENSE, 'package.json' and README.md.

Example

$ gen project:rootfiles

project

Scaffold out a basic node.js project. This task is run by the default task. Also, this task is aliased as project:project to simplify using this generator as a plugin in other generators.

Example

$ gen project
# or
$ gen project:project

gulp

Scaffold out basic project for a gulp plugin.

Example

$ gen project:gulp

base

Scaffold out a project for a base plugin.

Example

$ gen project:base

minimal

Scaffold out a minimal code project,

Example

$ gen project:min
# or
$ gen project:minimal

generator

Scaffold out a basic generate generator project.

Example

$ gen project:generator

helper

Scaffold out a basic template helper project.

Example

$ gen project:helper

Visit Generate's documentation for tasks.

Generated files

Files generated by each task. See the Generate customization docs to learn how to override individual templates.

(diffs are base on the files generated by the default task)

default

Files generated by the default task:

.
 ├── .editorconfig
 ├── .eslintrc.json
 ├── .gitattributes
 ├── .gitignore
 ├── .travis.yml
 ├── index.js
 ├── contributing.md
 ├── LICENSE
 ├── package.json
 └── README.md

files

Files generated by the files task:

.
 ├── .editorconfig
 ├── .eslintrc.json
 ├── .gitattributes
 ├── .gitignore
 ├── .travis.yml
-├── index.js
 ├── contributing.md
 ├── LICENSE
 ├── package.json
 └── README.md

index

Files generated by the index task:

.
-├── .editorconfig
-├── .eslintrc.json
-├── .gitattributes
-├── .gitignore
-├── .travis.yml
 └── index.js
-├── contributing.md
-├── LICENSE
-├── package.json
-└── README.md

dotfiles

Files generated by the dotfiles task:

.
 ├── .editorconfig
 ├── .eslintrc.json
 ├── .gitattributes
 ├── .gitignore
 └── .travis.yml
-├── index.js
-├── contributing.md
-├── LICENSE
-├── package.json
-└── README.md

rootfiles

Files generated by the rootfiles task:

.
-├── .editorconfig
-├── .eslintrc.json
-├── .gitattributes
-├── .gitignore
-├── .travis.yml
-├── index.js
 ├── contributing.md
 ├── LICENSE
 ├── package.json
 └── README.md

project

Files generated by the project task:

.
 ├── .editorconfig
 ├── .eslintrc.json
 ├── .gitattributes
 ├── .gitignore
 ├── .travis.yml
 ├── index.js
 ├── contributing.md
 ├── LICENSE
 ├── package.json
 └── README.md

gulp

Files generated by the gulp task:

.
 ├── .editorconfig
 ├── .eslintrc.json
 ├── .gitattributes
 ├── .gitignore
 ├── .travis.yml
 ├── index.js
+├── gulpfile.js
 ├── contributing.md
 ├── LICENSE
 ├── package.json
 └── README.md

base

Files generated by the base task:

.
 ├── .editorconfig
 ├── .eslintrc.json
 ├── .gitattributes
 ├── .gitignore
 ├── .travis.yml
 ├── index.js
 ├── contributing.md
 ├── LICENSE
 ├── package.json
 └── README.md

minimal

Files generated by the minimal task:

.
-├── .editorconfig
-├── .eslintrc.json
-├── .gitattributes
 ├── .gitignore
-├── .travis.yml
-├── index.js
-├── contributing.md
 ├── LICENSE
 ├── package.json
 └── README.md

generator

Files generated by the generator task:

.
 ├── .editorconfig
 ├── .eslintrc.json
 ├── .gitattributes
 ├── .gitignore
 ├── .travis.yml
-├── index.js
+├── generator.js
 ├── contributing.md
 ├── LICENSE
 ├── package.json
 └── README.md

helper

Files generated by the helper task:

.
 ├── .editorconfig
 ├── .eslintrc.json
 ├── .gitattributes
 ├── .gitignore
 ├── .travis.yml
 ├── contributing.md
 ├── LICENSE
 ├── package.json
 ├── README.md
 └── index.js

Next steps

Running unit tests

It's never too early to begin running unit tests. When you're ready to get started, the following command will ensure the project's dependencies are installed then run all of the unit tests:

$ npm install && test

Publishing your project

If you're tests are passing and you're ready to publish your project to npm, you can do that now with the following command:

Are you sure you're ready?!

$ npm publish

About

Related projects

• generate-dest: Prompts the user for the destination directory to use. Can be used from the command… more | homepage
• generate-install: Generator that automatically detects the dependencies or devDependencies to install based on the templates or… more | homepage
• generate-package: Generate] a package.json from a pre-defined or user-defined template. This generator can be used from… more | homepage

Community

Are you using Generate in your project? Have you published a generator and want to share your project with the world?

Here are some suggestions!

• If you get like Generate and want to tweet about it, please feel free to mention @generatejs or use the #generatejs hashtag
• Show your love by starring Generate and generate-project
• Get implementation help on StackOverflow (please use the generatejs tag in questions)
• Gitter Discuss Generate with us on Gitter
• If you publish an generator, thank you! To make your project as discoverable as possible, please add the keyword generategenerator to package.json.

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.

Please read the contributing guide for avice on opening issues, pull requests, and coding standards.

Running tests

Install dev dependencies:

$ npm install -d && npm test

Author

Jon Schlinkert

• github/jonschlinkert
• twitter/jonschlinkert

License

Copyright © 2016, Jon Schlinkert. Released under the MIT license.

This file was generated by verb-generate-readme, v0.1.28, on July 31, 2016.