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 🙏

© 2025 – Pkg Stats / Ryan Hefner

build-express-api

v1.2.4

Published

Command line interface for instantly building an express rest api

Readme

Build Express Api

A Command line interface for instantly building an express rest api. Create controllers, models and add routes in matter of seconds.

Build Status npm version

This CLI only supports Node 6 and over.

Installation

Install it once globally:

$ npm install -g build-express-api

Getting Started

Initializing the application structure

$ mkdir my-app
$ cd my-app
$ build-express-api init

Directory structure

my-app
├── package.json
├── beaConfig.json
├── rest
    └── controllers
    └── models
    └── server.js

Install all the needed dependencies:

$ npm install

Note: when running all of the further commands, please stay in the my-app directory

Configuring CLI with active projects

If you already started a project, and have a different application structure, no worries.

$ build-express-api create-config

or

$ build-express-api cconfig

This command only creates a beaConfig.json file in the root directory, without creating a ./rest folder. Use this file to configure the CLI on where to store the controllers, models, and where is the server.js or app.js file

beaConfig.json initially looks like this

{
  "serverPath": "./rest/server.js",
  "controllersPath": "./rest/controllers",
  "modelsPath": "./rest/models"
}

Configure the paths to your application, so the CLI knows how to execute the commands.

Creating a new controller

$ build-express-api create-controller

or

$ build-express-api cc

The CLI will now take you through series of questions, the example of building a new controller would be:

Creating a plain controller

You can choose the plain controller or custom routes controller from the menu.

Plain controller just creates a controller with built in routes in the path provided in beaConfig.json file.

Custom routes controller allows you to manually add your routes, the example of building custom routes controller would be:

Creating a custom routes controller

Note: make sure that you write the routes in the correct (strict JSON) format such as:

{"routeName":"METHOD"}

When the controller is created it will automatically be imported in the file provided in the beaConfig.json as the serverPath.

Adding routes to a controller

$ build-express-api add-routes <controllerName>

or

$ build-express-api ar <controllerName>

Example:

Adding routes to a controller

Creating new model

$ build-express-api create-model

or

$ build-express-api cm

Example:

Creating new model

Note: When creating new model, you don't need to provide the properties in strict JSON format, just separate them with the comma

Also models are not automatically imported in server.js, so you will need to import them manually.

This CLI supports only mongoose models for now.

Creating multiple controllers and models

If you need to instantly create multiple controllers, and models, you will need to define a schema object in beaConfig.json file. When defining schema, it must be in a correct format.

Example of beaConfig.json, with schema file:

{
  "serverPath": "./rest/server.js",
  "controllersPath": "./rest/controllers",
  "modelsPath": "./rest/models",
  
  "schema": {
    "controllers": [
      {
        "name": "foo1",
        "routes": "plain"
      },
      {
        "name": "posts",
        "routes": {
          "getPosts": "GET",
          "createNew": "POST"
        }
      }
    ],
    "models": [
      {
        "name": "User",
        "props": "username: String, password: String"
      },
      {
        "name": "Post",
        "props": "title: String, properties: { isRead: Boolean, DateCreated: Date }"
      }
    ] 
  }

}

As you can see, the controllers and models objects are defined as an array of objects containing information about every controller and model.

After the schema is defined, simply run

$ build-express-api build-schema

or

$ build-express-api bs

And the CLI will create all of the defined controllers, and models in the schema.

When defining schema, if you want to create plain controller, simply set the routes field to "plain", and if you want to add routes to a specific controller, you must define them like in the example above.

If you want to create only multiple controllers, just erase the models array. Same goes when creating only multiple models.

Notes

Note: The experience this CLI provides does not work as smooth in Git Bash terminal, since it is not an interactive terminal, but if you are using Git Bash inside VS Code, then there are no problems, I found no complications using any other terminal.

Feel free to post issues if you run into any.