Component Middewares Definition

A component can register any number of middleware handlers that will be called ordered by their weights in http posts and get calls for any request.

To do that, the hook Middleware is used in onStart component method:

MantraAPI.Hooks("<component name>")
        MiddlewareHandler: <function handler for the middleware>,
        Weight: <integer with the weight of the middleware, optional, default: 0>

As an example, consider this middleware registration:

        MiddlewareHandler: RedirectMiddlewareHandlers.CheckOrigin,
        Weight: -500

In this example, the method RedirectMiddlewareHandlers.CheckOrigin will be called in the middleware chain with a weight of -500.

Tip: you can check the middlewares registered by the project with the mantra command show-middlewares.

Brief method of defining middlewares

To avoid typing the hook regitering call in onStart method, you can describe the middlewares of the component in a specific module which file name should be named as "middleware.<component name>.js".

In this case, the module should define a number of properties named as the following:

  • "<middleware_name>_weight" (optional): weight of the middleware. Default is zero.
  • "<middleware_name>": middleware function handler

Middleware weights and order calling

When starting a Mantra application, the bootstrap process registers all middlewares in the order of their weights from lowest to highest.

If two middlewares have the same weight, the will be called with no specific order.

Function handler for the middleware

A Mantra middleware is exactly the same then Express middleware, so their handlers should be defined with a function like:

async (req,res,next) => {
    // ...

As Mantra posts and views handlers, req is the Request object of Express framework, res is the Response object of Express framework and next is a function to be called if the middleware chain should continue.