Skip to content

Http server abstraction that includes the minimal dependencies for a express-like API.

Notifications You must be signed in to change notification settings

sugojs/sugo-server

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

@sugo/server

Http server abstraction that includes the minimal dependencies for a express-like API. It extends the vanilla NodeJS Http Server, Http Request and Http Response.

Router agnostic. It is recommended to use with @sugo/router.

The server implements:

  • Request body extraction
  • Server middleware
  • URL parsing
  • Express-style Response Helper methods (status, json)
  • Error Handling

All this is implemented on a Server class that can be subclassed in order to extend it

SuGoServer

Options

  • @param {*} requestHandler: The NodeJS request handler

SuGoSecureServer

Options

  • @param {*} requestHandler: The NodeJS request handler
  • @param {*} options: The NodeJS https options

Requirements

node version >= 8.12.0

How to install

npm install --save @sugo/server

Creating a Http Server

A server can be created using the new Server() constructor, but it is recommended to use the createServer method unless you have the need to use new Server().

import { createServer, SuGoRequest, SuGoResponse, INextFunction } from '@sugo/server';
const server = createServer((req: SuGoRequest, res: SuGoResponse) =>
  res.status(200).json({ first: req.first, second: req.second }),
);
server.listen(3000);

Creating a Https Server

A server can be created using the new Server() constructor, but it is recommended to use the createServer method unless you have the need to use new Server().

import { createServer, SuGoRequest, SuGoResponse, INextFunction } from '@sugo/server';
const server = createSecureServer(
  (req: SuGoRequest, res: SuGoResponse) => res.status(200).json({ first: req.first, second: req.second }),
  {
    cert: fs.readFileSync(path.resolve(__dirname, 'server.cert')),
    key: fs.readFileSync(path.resolve(__dirname, 'server.key')),
  },
);
server.listen(3000);

Middleware

Middleware can be added for the whole server using the useMiddleware method. The middleware stack will start before the request handler, but the sequence be defined by the use of the next() function. This function calls the next function in the stack. Next is an async function.

import { createServer, SuGoRequest, SuGoResponse, INextFunction } from '@sugo/server';

const server = createServer((req: SuGoRequest, res: SuGoResponse) =>
  res.status(200).json({ first: req.first, second: req.second }),
);
server.useMiddleware(async (req: SuGoRequest, res: SuGoResponse, next?: INextFunction) => {
  req.foo = 'fighters';
  if (next) {
    await next();
  }
});
server.listen(3000);

Error handling

To keep the modularity of the lme modules (and because each project has different error handling needs), the error handling must be made through user middleware. We leave an example of such middleware for common cases.

IMPORTANT NOTE: The error handling middleware will only catch errors after it was set, so it should be the FIRST middleware to be set.

Example:

import { createServer, SuGoRequest, SuGoResponse, INextFunction } from '@sugo/server';
const server = createServer((req: SuGoRequest, res: SuGoResponse) =>
  res.status(200).json({ first: req.first, second: req.second }),
)
  .useMiddleware(async (req, res, next) => {
    try {
      await next();
    } catch (err) {
      const defaultValues = {
        code: 'N/A',
        message: 'Unexpected Error',
        name: err.name ? err.name : err.constructor.name ? err.constructor.name : 'Error',
        status: 500,
      };
      const json: any = Object.getOwnPropertyNames(err).reduce((obj, key) => {
        obj[key] = err[key];
        return obj;
      }, defaultValues);
      res.status(json.status).json(json);
    }
  })
  .listen(3000);

Request body extraction

To keep the modularity of the sugo modules and give our users more freedom, the body extraction must be handled with middleware. SuGoJS has the following middleware available:

Logging

To keep the modularity of the sugo modules (and because each project has different logging needs), the request logging must be made through user middleware. We leave an example of such middleware for common cases.

import { SuGoRequest, SuGoResponse } from '@sugo/server';
import * as util from 'util';

const logRequest = async (req: SuGoRequest, res: SuGoResponse, next?: () => any) => {
  let log: string = util.format('Request ID: ( %s ) %s: %s', req.id, req.method, req.url);
  log += util.format(' --> query %j', req.query);
  log += util.format(' --> body %j', req.body);
  logger.info(log);
  return next ? await next() : null;
};

const logResponse = async (req: SuGoRequest, res: SuGoResponse, next?: () => any) => {
  next ? await next() : null;
  const now = new Date().toISOString();
  const { id, statusCode, statusMessage, body, method, url } = res;
  const log = `${now}: Response ID: ( ${id} ) ${method}: ${url} ${statusCode} ${statusMessage} ---> body: ${JSON.stringify(
    body,
  )}`;
  if (statusCode >= 400) {
    logger.error(log);
  } else {
    logger.info(log);
  }
  return;
};

const server = createServer(HANDLER)
  .useMiddleware(logRequest)
  .useMiddleware(logResponse);
server.listen(3000);

Helper methods

  • res.json(data): Sets the response type to JSON and sends an JSON object.
  • res.status(status): Sets the status for the response
import { createServer, SuGoRequest, SuGoResponse } from '@sugo/server';
const server = createServer((req: SuGoRequest, res: SuGoResponse) =>
  res.status(200).json({ first: req.first, second: req.second }),
);
server.listen(3000);

Additional Properties - Request

  • id: Sets the response type to JSON and sends an JSON object.
  • path: An url striped down of hashes and queryparams. Example: "/foo?hello=world" would result in path being "/foo"
  • query: Parsed querystring stored as an object.
  • body: Parsed request body stored as an object.

Additional Properties - Response

For loggind purposes, we copy the id, path and method properties from the request.

Complete Application Example

import { createServer, SuGoRequest, SuGoResponse } from '@sugo/server';
import { Router } from '@sugo/router';
import * as cors from 'cors';

const router = new Router();
router.get('/foo', (req: SuGoRequest, res: SuGoResponse) => res.end(JSON.stringify({ foo: req.foo })));

// createServer is
const server = createServer(async (req: SuGoRequest, res: SuGoResponse) => await router.handle(req, res));

server.useMiddleware(async (req: SuGoRequest, res: SuGoResponse, next?: INextFunction) => {
  res.setHeader('Access-Control-Allow-Origin', '*');
  res.setHeader('Access-Control-Allow-Methods', 'GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS');
  res.setHeader('Access-Control-Max-Age', 2592000);
  if (next) {
    await next();
  }
});
server.listen(3000);

About

Http server abstraction that includes the minimal dependencies for a express-like API.

Resources

Stars

Watchers

Forks

Packages

No packages published