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-destiny

v3.1.0

Published

Express helper for dealing with middleware code paths

Downloads

5

Readme

Express-Destiny

Install:

npm install express-destiny

Express-Destiny is a simple express middleware, which allows middleware to be applied depending on different Accept header formats (exactly like res.format() just a little more convenient)

e.g.

var express = require('express')
var destiny = require('express-destiny')

var app = express()

app.use(destiny('json', function (req, res, next) {
  // do something if req.headers.Accept is a json format
}))

// alternatively you can add multiple

app.use(destiny({
  json: function (req, res, next) {
    // do something and return JSON
  },

  html: function () {
    // do something else and return HTML
  }
}))

// you can also parse an options object as the 2nd or 3rd argument...

destiny('json', function () {}, { default: false })

// or

destiny({ json: function () {} }, { default: false })

One thing it is worth noting, because older IE browsers send Accept: */* header when requesting html if you only specify JSON, this would cause for a request for HTML to return the JSON file attempting to download it to the user.

To deal with this issue we first ensure that the following mime-types are prioritised in the following order:

  • text
  • text/plain
  • html
  • text/html
  • default

No default handle is present then we create a default one, which calls next(). Usually un the default handle you have no access to the req, res, or next however this has been provided as an additional feature.

If you would like to disable this you can do so by using default: false option displayed in the example above.