From 168de9d15f49fd756db6be34ca15fe44c1be56ed Mon Sep 17 00:00:00 2001 From: Steve Konves Date: Thu, 15 Feb 2018 19:01:51 -0700 Subject: [PATCH] docs: update installation step --- README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 51f47d3..73c9b2c 100644 --- a/README.md +++ b/README.md @@ -12,11 +12,10 @@ # Express HTTP Context Get and set request-scoped context anywhere. This is just an unopinionated, idiomatic ExpressJS implementation of [cls-hooked](https://github.com/Jeff-Lewis/cls-hooked) (forked from [continuation-local-storage](https://www.npmjs.com/package/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+). -(Note: For node v4-7, use the legacy 0.x.x package version.) - ## How to use it -Install: `npm install --save express-http-context` +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. The earlier the better; you won't have access to the context from any middleware "used" before this one.