@crispengari/node-backend v2.0.1

Node backend.

This is a simple boiler plate command line tool that will generate a node backend boiler plate with either javascript or typescript express server ready to run.

Usage

To use this clt it is very easy all you have to do is to run the following command:

npx @crispengari/node-backend

OR Install it globally by running the following command

1. using yarn

yarn global  @crispengari/node-backend

2. using npm

npm install -g  @crispengari/node-backend

Then

You can run the initializer directly by running the following command:

@crispengari/node-backend

Generated folders and files.

- 📁 parent folder
    - 📁 src
        - 📁 routes
            - index.[j|s]
        - server.[j|s]
    - 🗄 .gitignore
    - 🗄 README.md
    - 🗄 package.json
    - 🗄 LISENSE (MIT)
    - 🗄 tsconfig.json (if typescript is selected as a language)

Staring the server.

Note: Starting the server is different if you are using typescript or javascript.

1. With JavaScript:

yarn|npm dev

Note- You can also use the following command to start the server but with no hot reloading:

yarn|npm start

2. With TypeScript:

With ts you have to open two command the one that will watch for file changes and the other one that will run the compiled javascript code: a) cmd 1

yarn|npm watch

b) cmd 2

yarn|npm dev

c). Or you can use a single command which: This command is built basically uses ts-node-dev. You can configure flags based on your preferences

yarn|npm start:fast

Note You can also use the following command to start the typescript server with an single command:

yarn|npm start

Installing and Executing specific versions

You can be able to install the specific versions of @crispengari/node-backend using either yarn or npm globally as follows:

1. using yarn

yarn add @crispengari/node-backend@<version>

# example (make sure the version exists before running this)
yarn add @crispengari/node-backend@<1.3.2>

2. using npm

npm install @crispengari/node-backend@<version>

# example (make sure the version exists before running this)
npm install @crispengari/node-backend@<1.3.2>

3. Running the node package executer npx

npx @crispengari/node-backend@<version>

# example (make sure the version exists before running this)
npx @crispengari/node-backend@<1.3.2>

Available working versions

v1

1. @crispengari/node-backend@1.3.2
2. @crispengari/node-backend@1.3.6
3. @crispengari/node-backend@1.3.7
4. @crispengari/node-backend@1.3.8

v2

1. @crispengari/node-backend@2.0.1