This is a boilerplate application for building REST APIs in Node.js using ES6, Express and PostgreSQL.
- Clone the repository with
https://github.com/japananh/node-express-postgres-boilerplate.git - Install the dependencies with
yarn install(click here if you don't have Yarn installed - Setup the database on
src/config/postgres.jsand config information onenv.example
This boilerplate comes with a collection of npm scripts to make your life easier, you'll run them with npm run <script name> or yarn <script name>:
dev: Run the application in development modelint: Run ESLintlint:fix: Fix ESLint errorsprettier: Run prettierprettier:fix: Fix prettier errors
src\
|--config\ # Environment variables and configuration related things
|--controllers\ # Route controllers (controller layer)
|--db\
|--config\ # Configuration for database
|--migrations\ # Database migrations
|--models\ # Database models
|--seeders\ #
|--docs\ # Swagger files
|--middlewares\ # Custom express middlewares
|--routes\ # Routes
|--services\ # Business logic (service layer)
|--utils\ # Utility classes and functions
|--validations\ # Request data validation schemas
|--app.js # Express app
|--index.js # App entry point
To view the list of available APIs and their specifications, run the server and go to http://localhost:3000/v1/docs in your browser. This documentation page is automatically generated using the swagger definitions written as comments in the route files.
List of available routes:
Auth routes:
POST /v1/auth/register - register
POST /v1/auth/login - login
POST /v1/auth/forgot-password - forgot-password
POST /v1/auth/reset-password - reset-password
User routes:
POST /v1/users - create a user
GET /v1/users - get all users
GET /v1/users/:userId - get user
PATCH /v1/users/:userId - update user
DELETE /v1/users/:userId - delete user
Role routes:
POST /v1/roles - create a role
GET /v1/roles - get all roles
GET /v1/roles/:roleId - get a role
PATCH /v1/roles/:roleId - update a role
DELETE /v1/roles/:roleId - delete a role
This app uses Sequelize - an Object-Relational Mapper to maps object syntax into Postgres database, and Sequelize CLI package to manage sequelize.
There are 2 ways to run sequelize-cli.
# Method 1: Use sequelize global
npm install -g sequelize-cli
sequelize db:migrate
# Method 2
node_modules/.bin/sequelize db:migrateThe app has a centralized error handling mechanism.
Controllers should try to catch the errors and forward them to the error handling middleware (by calling next(error)). For convenience, you can also wrap the controller inside the catchAsync utility wrapper, which forwards the error.
const catchAsync = require('../utils/catchAsync');
const controller = catchAsync(async (req, res) => {
// this error will be forwarded to the error handling middleware
throw new Error('Something wrong happened');
});The error handling middleware sends an error response, which has the following format:
{
"code": 404,
"message": "Not found"
}When running in development mode, the error response also contains the error stack.
The app has a utility ApiError class to which you can attach a response code and a message, and then throw it from anywhere (catchAsync will catch it).
For example, if you are trying to get a user from the DB who is not found, and you want to send a 404 error, the code should look something like:
// user.controller.js
const httpStatus = require('http-status');
const ApiError = require('../utils/ApiError');
const getUser = catchAsync(async (req, res) => {
const user = await userService.getUserById(req.params.userId);
if (!user) {
throw new ApiError(httpStatus.NOT_FOUND, 'User not found');
}
res.send({ user });
});Request data is validated using Joi. Check the documentation for more details on how to write Joi validation schemas.
The validation schemas are defined in the src/validations directory and are used in the routes by providing them as parameters to the validate middleware.
const express = require('express');
const validate = require('../../middlewares/validate');
const userValidation = require('../../validations/user.validation');
const userController = require('../../controllers/user.controller');
const router = express.Router();
router.post(
'/users',
validate(userValidation.createUser),
userController.createUser
);To require authentication for certain routes, you can use jwt function at config folder
// app.js
const jwt = require('./config/jwt');
app.use(jwt());These routes require a valid JWT access token in the Authorization request header using the Bearer schema. If the request does not contain a valid access token, an Unauthorized (401) error is thrown.
The auth middleware is used to require certain rights/permissions to access a route.
const express = require('express');
const { grantAccess } = require('../../middlewares/validateAccessControl');
const validate = require('../../middlewares/validate');
const userValidation = require('../../validations/user.validation');
const userController = require('../../controllers/user.controller');
const router = express.Router();
router
.route('/')
.get(
grantAccess('readAny', 'user'),
validate(userValidation.getUsers),
userController.getUsers
);In the example above, an authenticated user can access this route only if that user has the getUsers permission.
The permissions are role-based. You can view the permissions/rights of each role in the src/config/roles.js file.
If the user making the request does not have the required permissions to access this route, a Forbidden (403) error is thrown.
Import the logger from src/utils/logger.js. It is using the Winston logging library.
Logging should be done according to the following severity levels (ascending order from most important to least important):
const logger = require('<path to src>/utils/logger');
logger.error('message'); // level 0
logger.warn('message'); // level 1
logger.info('message'); // level 2
logger.http('message'); // level 3
logger.verbose('message'); // level 4
logger.debug('message'); // level 5In development mode, log messages of all severity levels will be printed to the console.
In production mode, only info, warn, and error logs will be printed to the console.
It is up to the server (or process manager) to actually read them from the console and store them in log files.
This app uses pm2 in production mode, which is already configured to store the logs in log files.
Note: API request information (request url, response code, timestamp, etc.) are also automatically logged (using morgan).
To be updated