npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

express-request-context

v1.0.1

Published

Enable contexts in express Request and Response objects

Downloads

4,275

Readme

express-request-context

A tiny addon to ExpressJS to help you pass data along with the Request and Response objects in your route handlers.

Quick Start

This is a Node.js package available through the npm registry. Installation into your project is done with the npm install command:

npm install --save express-request-context

Now add our middleware to your ExpressJS app:

import expressContext from "express-request-context";

const app = express();

app.use(expressContext()); // This will enable the 'context' object for you.

In your route handler, you now have a context object available in which you can shove any object or data that gets transferred to the next route handler. For example, you can get some user data from your database and use it in your next route:

Router.use((req, res, next) => {
	const userData = db.getUserByToken(req.headers.authorization);
   req.context.userData = userData;
   next();
});

Philosophy

Have you ever been building an ExpressJS backend and encoutered the problem that you want to pass some data along with the Request and Response objects to the next route handler? Right, there's no such thing as extending those objects and adding your own stuff to it (in Typescript).

Example:

Router.use((req, res, next) => {
    const accessToken = req.headers.authorization.token.replace("Bearer ", "");
    const userData = getUserDataFromAccessToken(accessToken);
    
    /*
    The userData object now contains some data about the user that we want to use else where to:
    - Check permissions
    - Check ownership of a resource
    - Compare ids or passwords
    - Etc.
    
    And we also need the accessToken for future stuff.
    But how to pass these things along to the next handler?
    */
    
    req.user = userData; 		// !
    res.token = accessToken 	// !

    next();
});

This won't work when you're using Typescript, because it will throw the following error:

TSError: ⨯ Unable to compile TypeScript:
src/myRouteHandler.ts:124:9 - error TS2339: Property 'user' does not exist on type 'Request<ParamsDictionary>'.

124                     req.user = userData;
                            ~~~~
src/myRouteHandler.ts:124:9 - error TS2339: Property 'token' does not exist on type 'Request<ParamsDictionary>'.

125                     req.token = token;
                            ~~~~~

Cause the user and token property don't exist on the Request object.

Solution

This package adds a context object of type any to both the Request and Response objects of ExpressJS. You can then put whatever you like in there to include with the Request in the next route handler:

Router.use((req, res, next) => {
    const accessToken = req.headers.authorization.token.replace("Bearer ", "");
    const userData = getUserDataFromAccessToken(accessToken);
    
    req.context.user = userData; 	// !
    res.context.token = accessToken	// !

    next();
});

The only thing you need to do to get started is add the middleware in this package to your ExpressJS app:

import expressContext from "express-request-context";

const app = express();

app.use(expressContext()); // This will enable the 'context' object for you.

Happy hacking!

Contributing

Feel free to open an issue or a pull request in the repo on GitHub!

License

MIT