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

generator-omaha

v8.2.0

Published

Yeoman generator designed to help you craft sustainable code for the modern web

Downloads

8

Readme

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

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:

See the full webapp tech stack here

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

  • servers built on express with security baked in (using lusca and helmet)
  • plugins to support a modular architecture
  • projects with pre-configured modern workflows
  • native desktop applications built on Electron --> quickly turn your web app into a desktop app!

Typical Workflows

After scaffolding a new project with yo omaha ...

  • Serve live-reload enabled app with companion RESTful API using npm start, then...
    • :sparkles: lint your code in real-time with a second terminal running npm run lint:watch
    • :100: run tests and calculate code coverage in real-time with npm run test:watch
    • :lipstick: see your style updates and code changes in the browser with a second terminal running grunt styling
  • Run tests with npm test
  • One-time lint with npm run lint
  • Run tests and lint code as a watch task in one terminal with: npm run dev (linux only)
  • Demo your bundled project in a browser with npm run demo
  • View reports, documentation and styleguide:
    • code coverage: grunt cover open:coverage
    • Plato report: grunt plato open:plato
    • JSDocs documentation: grunt docs open:docs
    • Living styleguide: grunt docs open:styleguide
  • Review the code to see all the available tasks

View the technologies used and the lint rules that make your code more secure

Command Line Options

Beyond yo omaha --help

  • Scaffold a web app after making some choices via prompts (options are not honored without the use of --defaults)
yo omaha
  • Scaffold a web app "auto-magically" with defaults and no user input
yo omaha --defaults
  • Use "silent" webapp defaults, skip support for everything, and select custom source directory
yo omaha --defaults --slim --src src
  • Use "silent" web app defaults with Webpack
yo omaha --defaults --use-webpack
yo omaha --defaults --use-browserify --use-jest
  • Use "silent" web app defaults with custom modifications
yo omaha --defaults --template-technology lodash --skip-coveralls

Available options

Default in bold

  • --defaults: scaffold app with no user input using defaults
  • --slim: use with --defaults to skip install of support for benchmark, coveralls, jsinspect, aria, and imagemin
  • --src: use with --defaults to select custom source directory for app and assets files
  • --amd: use AMD module format (with r.js as script bundler)
  • --use-browserify: use Browserify as script bundler (auto selects CommonJS module format)
  • --use-jest: use Facebook's Jest instead of mocha (auto selects CommonJS module format)
  • --use-webpack: use Webpack as script bundler (auto selects CommonJS module format and Jest test framework)
  • --use-rust: Add folder structure, sample file, and build scripts for WebAssembly development using Rust (rustc and wasm-gc required)
  • --skip-benchmark: use with --defaults
  • --skip-coveralls: use with --defaults
  • --skip-jsinspect: use with --defaults
  • --skip-aria: use with --defaults
  • --skip-imagemin: use with --defaults
  • --css-preprocessor: less | sass | none
  • --template-technology: handlebars | lodash

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