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

@midwest/responder

v0.2.1

Published

One of the main concepts behind Midwest is a global responder middleware. Basically no other middleware should be sending the response, they should simply call `next()` until the responder is reached. The responder then either send the contents of `res.lo

Downloads

7

Readme

Midwest Responder

One of the main concepts behind Midwest is a global responder middleware. Basically no other middleware should be sending the response, they should simply call next() until the responder is reached. The responder then either send the contents of res.locals as JSON or renders a template.

Only the global responder should ever be terminating a request (ie. send a response).

The responder is a very short and simple middleware that decides what to send back to the client.

Usage

const errorHandler = require('@midwest/error-handler')(config.errorHandler)

server.use([
  require('midwest/middleware/ensure-found'),
  // format and log error
  errorHandler,
  // respond
  require('@midwest/responder')({
    errorHandler,
    logError: require('@midwest/error-handler/log'),
  }),
])

Rendering

When the responder renders, calls the the render method:

res.render(res.master, ...(res.templates || []))

Master vs Template

The master is the template that contains the <html>, <head> and <body> tags. It includes scripts, styles etc.

Prevent Flattening

If there is only a single property on the res.locals object, the responder will send that property directly. Ie. if res.locals = { poopsicle: {...} } {...} will be sent instead of { poopsicle: {...} }.

Caveats

Static routes also matching dynamic routes

Since no middleware except the responder should be sending the response, dynamic routes that match static routes will clash.

Ie. if you have

server.get('/api/users/me', mw.getCurrent)
server.get('/api/users/:id', isAdmin, mw.findById)

and make a request to /api/users/me, the isAdmin and mw.findById middleware will always be called after mw.getCurrent. If the user is not an admin, all requests to /api/users/me will return the 401 response from isAdmin middleware.

To prevent this, create a Express#param function like so:

router.param(':id', (req, res, next, id) => {
  if (id === 'me')
    return next('route')

  next()
})