node-execution-context

A straightforward library that provides a persistent process-level context wrapper using node "async_hooks" feature.

Installation

npm i node-execution-context

Getting started

Let't start with creating the context initialisation point of our app, well take an simples express app for this example

// main.js

const express = require('express');
const Context = require('node-execution-context');
const UserController = require('./controllers/user');
const app = express();
const port = 3000;

const ContextMiddleware = (req, res, next) => {
    Context.run(next, { val: true });
};

app.use('/', ContextMiddleware);
app.post('/user', UserController.create);

app.listen(port);

This will expose any point of your code form this point that handles that request.

// ./controller/user/index.js

const Context = require('node-execution-context');
const mongo = require('../service/mongo');
const logger = require('../service/logger');

export class UserController {
    async create (req) {
        const { user } = req.body;
        
        // This will return the reference number set by out ContextMiddleware
        const { reference } = Context.get();
        
        logger.info('Created user for reference: ', reference);
        
        return await mongo.create('user', user);
    }
}

API

create(initialContext?: object, domain? :string)

Creates for the current async resource an execution context entry identified with his asyncId. Any future processes that will be added to the async execution chain will be exposed to this context.

When passing custom domain to this method, the trigger point and all of it's sub processes will be exposed to a standalone context and won't effect / be effected by root context.

update(update: object)

Updates the current execution context with a given update obect.

get()

Returns the current execution context identified with the current asyncId.

run(fn: Function, initialContext: object)

Runs a given function under a dedicated AsyncResource, exposing given initial context to the process and it's child processes.

configure(config: ExecutionContextConfig) : void

Configures execution context settings.

monitor(): ExecutionMapUsage

Returns an monitoring report over the current execution map resources

Before calling monitor, you should configure execution context to monitor it's nodes. by default the data kept is as possible.

const Context = require('node-execution-context');

// Startup
Context.configure({ monitor: true });


// Later on
const usage = Context.monitor();
console.log(usage); // Prints execution context usage report.

API Usage

const Context = require('node-execution-context');

Context.create({
    value: true
});

Promise.resolve().then(() => {
    console.log(Context.get()); // outputs: {"value": true}
    
    Context.update({
        value: false
    });
    
    return new Promise((resolve) => {
        setTimeout(() => {
            console.log(Context.get()); // outputs: {"value": false}
            
            Context.update({
                butter: 'fly'
            });
            
            process.nextTick(() => {
                console.log(Context.get()); // outputs: {"value": false, "butter": 'fly'}
                resolve();
            });
            
        }, 1000);
        
        console.log(Context.get()); // outputs: {"value": true}
    });
});

The following errors can be thrown while accessing to the context API :

Code	When
CONTEXT_ALREADY_DECLARED	When trying to create execution context, but current async resource already exists.
CONTEXT_DOES_NOT_EXISTS	When try to get / update the context, but it yet been created.
MONITOR_MISS_CONFIGURATION	When try to monitor without calling configure with monitoring option.