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

jwt-express-decode

v0.1.2

Published

jwt decoding used with expess config

Downloads

3

Readme

jwt-express-decode

Middleware to decode incoming request in Express

Usage

npm install jwt-express-decode

Configuring options

Required

The params object must be given as the first argument or an error will be passed along next(error)

  1. params.secret = Your JWT token secret.
  2. params.header = the property on the header of the incoming where the JWT can be found.

Not Required

  1. params.req = this property name will be attached to the request and set to the decoded token, will be set to req.token if no value is passed in.
  2. Whitelist = array of request url's that will not need JWT protection. It's important to remember that when using Express mounting, Express will strip away the pre fixed mounted url before the url is inside the middleware. So app.use('/api', doSomething()). Inside of the doSomething() middleware, req.url will not include /api. So if we sent a request to /api/users/all the url inside doSomething will be /users/all.
exports.doSomething = function(req, res, next){
  req.url === // '/users/all'  
}

This is important to remember when including a whitelist of url's. You have to make sure you don't include the mounted prefix on the url's you're wanting to whitelist. So in this case, we would not include the /api prefix to the url's in the array, because we will use app.use('/api', decode(params, ['/users/new'])

Now in your server config

var express   = require('express'),
      decode  = require('jwt-express-decode'),
      app     = express();

var params = {
  secret: process.env.JWT_SECRET,
  header: 'token',
  req: 'token'
};

// white list request that we don't want to lock down with JWT like new user
// signup
var whitelist = ['/user/new', 'user/verify']

app.use('/api', decode(params, whitelist));