The best practice of building Koa2 with TypeScript. 中文

This layout requires NodeJS v12+

1. Run npm init koa-ts.

2. Install dependencies: yarn or npm i.

3. Start the server: yarn dev or npm dev. visit: http://127.0.0.1:3000/apis/sessions

(Optional) if you need database, set useDatabase to true.(in configs/customs.ts).

(Optional) the project has built-in a docker-compose, run npm run mongo lift mongodb automatic.

├── app
│   ├── controllers         ---  server controllers
│   ├── helpers             ---  helper func (interceptor / error handler / validator...)
│   ├── jobs                ---  task (periodic task / trigger task / email server...)
│   ├── entities            ---  database entities/models
│   └── services            ---  adhesive controller and model
├── config
│   ├── environments        ---  environment variable
│   ├── koa.middlewares     ---  middlewares for Koa
│   ├── routing.middlewares ---  middlewares for Routing Controller
│   ├── routing.options     ---  configs for Routing Controller
│   ├── connection          ---  database connection
│   ├── bootstrap           ---  lifecycle
│   ├── customs             ---  user settings
│   └── interceptors        ---  global interceptor
│   └── utils               ---  pure functions for help
└── test                    ---  utils for testcase
├── variables.env           ---  environment file

• Separation configuration and business logic.

• Export scheme model and interface, follow style of TypeScript.

• Test cases and lint configuration.

• The best practice for Dependency Injection in Koa project.

• Deploy by ncc.

• TypeScript hotload.

1. app.ts -> collect env vars environments -> collect env files variables.env

2. envs ready, call bootstrap.before()

3. configs/connection.ts connecting external services (e.g. DB / Redis...)

4. lift routing-controllers -> lift Koa middlewares -> register Container for DI

5. start Koa & invoke bootstrap.after() after startup

6. configs/connection.ts connected -> invoke bootstrap.connected()

You can link multiple databases (mysql / mongo etc.), each database can link configurations of multiple environments:

1. The database will load the configs of ormconfig.js file.
2. You can specify link configs of multiple environments under folder configs/environments.
3. You can specify encrypted information in file variables.env. It is not recommended to add file variables.env to version control.
4. You can still manually set process.env to override all environment variables.

• Development Mode (NODE_ENV=development): read configurations from configs/environments/development.ts file, but it will still be overwritten by variables.env file.

• Production Mode (NODE_ENV=production): read configurations from configs/environments/production.ts file, but it will still be overwritten by variables.env file.

• Parameter Validation
• routing-controllers
• typedi
• typeorm

This project is licensed under the MIT License. See the LICENSE file for more info.