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 🙏

© 2026 – Pkg Stats / Ryan Hefner

susanoo-ignite

v1.9.0

Published

A funky CLI tool for creating folder structures with ease.

Readme

Ignite CLI

Ignite CLI is a powerful tool designed to bootstrap entities for projects built using the Susanoo Express Framework. It provides an intuitive way to generate scaffolds for models, DAOs, handlers, controllers, and migrations, helping you kickstart your development process with ease and consistency.

Features

  • Generate scaffolds for various entities like models, DAOs, handlers, controllers, and migrations.
  • Supports creating scaffolds for all or specific entities at once.
  • Allows customization through a templates folder.
  • Includes trace and logging capabilities for debugging and clarity.

Installation

npm install susanoo-ignite --save-dev  && npm link susanoo-ignite

Usage

The Ignite CLI command is ignite. Below are the available commands and their usage:

General Syntax

ignite [options] <command>  

Options

  • -t, --trace
    Display trace statements for commands. Useful for debugging.

Commands

Generate Scaffolds

ignite g [type] -n <name> [options]  
  • Description:
    Generate scaffolds for models, DAOs, handlers, controllers, migrations, or all of them.

  • Arguments:

    • type: The type of scaffold to generate. Possible values:
      • model: Generate a model scaffold.
      • dao: Generate a DAO scaffold.
      • handler: Generate a handler scaffold.
        • handler:create|update|get|list|delete: To generate one handler
      • controller: Generate a controller scaffold.
      • migration: Generate a migration scaffold.
      • all OR LEAVE IT EMPTY: Generate all scaffolds.
  • Options:

    • -n, --name <name> (required): Name of the entity (e.g., AdvertisingNetwork).
    • -v, --version <version>: API version (default: v1).
    • -e, --entity <entity>: Entity folder (default: app).
  • Example Commands:
    Generate all scaffolds for an entity:

    ignite g all -n AdvertisingNetwork  

    Generate a specific scaffold (e.g., model):

    ignite g model -n AdvertisingNetwork  

    Generate multiple scaffolds (e.g., model and handler):

    ignite g model,handler -n AdvertisingNetwork  

Custom Templates

Ignite CLI creates a templates folder inside an ignite directory in your project. This allows you to customize the default templates for generated scaffolds.

How to Use Custom Templates

  1. Locate the templates folder:
    After running the CLI for the first time, you will find a folder structure like this in your project:

    ignite/
      templates/
        model.js
        dao.js
        handler.js
        controller.js
        migration.js
  2. Edit Templates:

    • Modify the files within each folder to match your project's coding style or specific requirements.
    • Future scaffolds will use these customized templates.
  3. Restore Defaults:

    • If you need to restore the default templates, simply delete the customized files. The CLI will fallback to the default version of them.

Debugging and Logs

  • Use the --trace option to enable detailed logs for commands:

    ignite g all -n AdvertisingNetwork --trace  
  • Logs include:

    • Command execution details.
    • Arguments and options passed.
    • Success or error messages for each scaffold.

Contributing

Feel free to contribute to the project by submitting issues or pull requests to the GitHub repository.


License

This project is licensed under the MIT License.