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-context-store

v0.3.2

Published

Store data related to current request without polluting request object

Downloads

1,024

Readme

express-context-store

Store data related to current request without polluting request object

Build Status

Install

yarn add express-context-store
# or
npm install express-context-store

Usage

const express = require('express');
const context = require('express-context-store');

const app = express();
app.use(context());

app.use((req, res, next) => {
  req.context.set('key', 'value');
  next();
});

app.get('/', (req, res, next) => {
  const value = req.context.get('key');
  res.send(value);
});

express-context-store uses Map under the hood with different API for .get and .set, so you can actually use Map method to req.context:

app.get('/', (req, res, next) => {
  // you can get the size
  console.log(req.context.size);
  // or check whether key is exists
  console.log(req.context.has('key'));
  // or get iterable for all entries
  console.log(req.context.entries());
});

Keep in mind that the value stored inside the map is actually an object that contains the value that you provide in .set method. This is why we provide .toObject method to get the actual value from the map. See serialization below

Rewrite context values

By default, context values are meant to be read only. Any attempt to override its value will throw error, for example:

app.use((req, res, next) => {
  req.context.set('a', 'b');
  req.context.set('a', 'c'); // throw error
});

This default behavior is implemented to prevent surprise when reading context key. If you want to change its behavior, you need to pass third option argument in .set method called writable:

app.use((req, res, next) => {
  req.context.set('a', 'b', { writable: true });
  // you need to pass writable: true again if you want to modify it later
  req.context.set('a', 'c', { writable: true });
});

Serialization

You can convert context store to plain javascript object by calling .toObject method. This is useful where you want to log current request context using JSON logger.

app.use((req, res, next) => {
  const context = req.context.toObject();
  JSONLogger.log(context);
});

Custom property name

If for some reason you can't use req.context, you can change the default property name by passing option object when creating the middleware:

const context = require('express-context-store');

// use req.data instead of req.context
app.use(context({ property: 'data' }));

app.use((req, res, next) => {
  req.data.set('key', 'value');
  next();
});

app.get('/', (req, res, next) => {
  const value = req.data.get('key');
  res.send(value);
});

License

MIT