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-memjs-cache

v1.0.0

Published

Mem.js cache middleware for Express

Downloads

27

Readme

express-memjs-cache

This is an Express middleware that caches responses using the MemJS memcached client.

Installation

  1. Set up your Express project

  2. Install the express-memjs-cache npm package:

    npm install express-memjs-cache
  3. Add the Memcachier Heroku add-on to your app

Setup

Place the middleware before your Express response handler(s):

const express = require('express')
const cache = require('express-memjs-cache')
const app = express()
  .use(cache({ cacheMaxAge: 60 }))
  .get('/widgets', expensiveListWidgets)

In this arrangement, responses will be cached using the URI (request.originalUrl, which includes the query string) as the cache key. The first request will miss the cache and set the cache key to the sent response body. Subsequent requests to the same URL will "hit" the cache and respond with the cached response body until the cached entry's age is at or above the cacheMaxAge (in this case, 60 seconds).

Cache keys

The default cache key of the request.originalUrl should serve most uses cases, but you can customize the cache key in a couple of different ways to suit your needs.

Regardless of how you do it, you will need to calculate the cache key before the cache middleware runs. The cache needs the cache key to determine whether it can serve the request, but it also needs the your handler(s) to generate a response body to cache.

  1. Provide your own getCacheKey option as a function that takes the Express request and response objects as arguments and returns a string.

  2. Set the x-cache-key response header. As with a custom getCacheKey function, you will need to set this header in a handler or middleware before the cache.