npmpackage.info

Gathering detailed insights and metrics for express-http-context-no-leak

express-http-context-no-leak - 1.2.6-4 | npmpackage.info

express-http-context-no-leak

Get and set request-scoped context anywhere

1.2.6-4

306

MIT

JavaScript

7.80 kB

4.9

Installations

npm install express-http-context-no-leak

Developer Guide

BETA

Typescript

No

Module System

CommonJS, UMD

Min. Node Version

>=8.0.0 <10.0.0 || >=10.4.0

Node Version

10.15.3

NPM Version

6.4.1 Pull Requests

Open

1

Total

46

Closed

10

Merged

35

Issues

Open

6

Total

39

Closed

33

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

skonves

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

306 Stars

119 Commits

27 Forks

10 Watchers

19 Branches

10 Contributors

Updated on Jul 03, 2025

Maintainers

View All 10 Contributors

Package Meta Information

Latest Version

1.2.6-4

Package Id

express-http-context-no-leak@1.2.6-4

Unpacked Size

7.80 kB

Size

3.41 kB

File Count

NPM Version

6.4.1

Node Version

10.15.3

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@types/cls-hooked @types/express als-context-test

Dev Dependencies

chai coveralls express istanbul mocha mocha-lcov-reporter supertest

Express HTTP Context

Get and set request-scoped context anywhere. This is just an unopinionated, idiomatic ExpressJS implementation of cls-hooked (forked from continuation-local-storage). It's a great place to store user state, claims from a JWT, request/correlation IDs, and any other request-scoped data. Context is preserved even over async/await (in node 8+).

How to use it

Install: npm install --save express-http-context
(Note: For node v4-7, use the legacy version: npm install --save express-http-context@<1.0.0)

Use the middleware immediately before the first middleware that needs to have access to the context. You won't have access to the context in any middleware "used" before this one.

Note that some popular middlewares (such as body-parser, express-jwt) may cause context to get lost. To workaround such issues, you are advised to use any third party middleware that does NOT need the context BEFORE you use this middleware.

1var express = require('express');
2var httpContext = require('express-http-context');
3
4var app = express();
5// Use any third party middleware that does not need access to the context here, e.g. 
6// app.use(some3rdParty.middleware);
7app.use(httpContext.middleware);
8// all code from here on has access to the same context for each request

Set values based on the incoming request:

1// Example authorization middleware
2app.use((req, res, next) => {
3	userService.getUser(req.get('Authorization'), (err, result) => {
4		if (err) {
5			next(err);
6		} else {
7			httpContext.set('user', result.user)
8			next();
9		}
10	});
11});

Get them from code that doesn't have access to the express req object:

1var httpContext = require('express-http-context');
2
3// Somewhere deep in the Todo Service
4function createTodoItem(title, content, callback) {
5	var user = httpContext.get('user');
6	db.insert({ title, content, userId: user.id }, callback);
7}

You can access cls namespace directly as (it may be useful if you want to apply some patch to it, for example https://github.com/TimBeyer/cls-bluebird):

1var ns = require('express-http-context').ns;

Troubleshooting

To avoid weird behavior with express:

Make sure you require express-http-context in the first row of your app. Some popular packages use async which breaks CLS.

For users of Node 10

Node 10.0.x - 10.3.x are not supported. V8 version 6.6 introduced a bug that breaks async_hooks during async/await. Node 10.4.x uses V8 v6.7 in which the bug is fixed. See: https://github.com/nodejs/node/issues/20274.

See Issue #4 for more context. If you find any other weird behaviors, please feel free to open an issue.

Contributors

Steve Konves (@skonves)
Amiram Korach (@amiram)
Yoni Rabinovitch (@yonirab)
DontRelaX (@dontrelax)
William Durand (@willdurand)

Interesting in contributing? Take a look at the Contributing Guidlines

SAST

Determines if the project uses static code analysis.

Score

4.9

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More