
Security News
/Research
npm Phishing Email Targets Developers with Typosquatted Domain
A phishing attack targeted developers using a typosquatted npm domain (npnjs.com) to steal credentials via fake login pages - watch out for similar scams.
node-execution-context
Advanced tools
Provides execution context wrapper for node JS, can be used to create execution wrapper for handling requests and more
A straightforward library that provides a persistent process-level context wrapper using node "async_hooks" feature.
npm i node-execution-context
Let't start with creating the context initialisation point of our app, well take an simples express app for this example
// main.js
const Context = require('node-execution-context');
const express = require('express');
const UserController = require('./controllers/user');
const app = express();
const port = 3000;
const ContextMiddleware = (req, res, next) => {
Context.create({
reference: req.body.reference
});
next();
};
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, res, next) {
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);
}
}
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.
Updates the current execution context with a given update obect.
Returns the current execution context identified with the current asyncId.
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. |
FAQs
Provides execution context wrapper for node JS, can be used to create execution wrapper for handling requests and more
The npm package node-execution-context receives a total of 0 weekly downloads. As such, node-execution-context popularity was classified as not popular.
We found that node-execution-context demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
/Research
A phishing attack targeted developers using a typosquatted npm domain (npnjs.com) to steal credentials via fake login pages - watch out for similar scams.
Security News
Knip hits 500 releases with v5.62.0, refining TypeScript config detection and updating plugins as monthly npm downloads approach 12M.
Security News
The EU Cyber Resilience Act is prompting compliance requests that open source maintainers may not be obligated or equipped to handle.