omahajs / generator-omaha

Yeoman generator designed to help you craft sustainable code for the modern web
https://omaha.js.org
MIT License
12 stars 1 forks source link
electron generator generator-omaha marionettejs native omaha scaffold yeoman
OMAHA JS
Travis-CI Build Status Codecov Coverage Status Package Quality CodeFactor Quality Score


A Yeoman generator for the modern front-end artisan designed to help you craft sustainable code for the web.

Quick Start

✔ Install Yeoman CLI tool, Grunt CLI tool, and generator-omaha node module globally

npm install --global yo grunt-cli generator-omaha

✔ Create an empty directory and cd into it

mkdir my-project && cd my-project

✔ Run omaha generator

yo omaha

✔ Make some choices

Generator Choices Rail Diagram


✔ Start creating your app!

omaha generator quick start asciicast

Patterns are Paramount

generator-omahastrives to enable developers of various skill and experience to more easily implement patterns and architectures with minimal time and effort. Specifically, generator-omaha enables the following patterns and capabilities:

The default sub-generator may be for a web app, but generator-omaha also has sub-generators for crafting:

Typical Workflows

After scaffolding a new project with yo omaha ...

View the lint rules that make your code more secure

Command Line Options

Beyond yo omaha --help

yo omaha
yo omaha --defaults
yo omaha --defaults --slim --src src
yo omaha --defaults --use-webpack
yo omaha --defaults --use-browserify --use-jest
yo omaha --defaults --template-technology lodash --skip-coveralls

Available options

Default in bold

But wait, there's more! Read about all the available generators!

Alternatives

Credits

A Note on Semantic Versioning

This project strives to follow the principles of semantic versioning (semver). However, it seems unreasonable to release major versions for changes to the generated output of generator-omaha that are not backwards compatible with the generated output of previous versions. In general, this project will release major versions when the generator API is not backwards compatible or when the generated outputs undergo substantial changes. In the case of the latter, a major version increment would serve more as a signifier of significant change (not necessarily changes that are not backwards compatible). I am perhaps making this more complicated than necessary; however, I want to avoid superficial "churn" while still maintaining a standardized process for development and enhancement.

License

FOSSA Status