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 🙏

© 2026 – Pkg Stats / Ryan Hefner

az-func-middleware

v1.0.3

Published

Simple middleware for Azure Functions

Readme

master

az-func-middleware

Simple middleware for Azure Functions

Installation

npm install az-func-middleware

Usage

Let's say you have the following HTTP Trigger:

const httpTrigger: AzureFunction = async function (context: Context): Promise<void> {
  context.res = {
    body: "This HTTP triggered function executed successfully."
  }
}

export default httpTrigger

You can simply wrap it using the withMiddleware function and pass an array of middlewares:

import { withMiddleware, Next } from 'az-func-middleware'

const myMiddleware = async (context: Context, next: Next) => {
  // run your logic
  // ...

  // call next() whenever you want to invoke the next middleware in the chain
  await next(context)
}

export default withMiddleware(httpTrigger, [myMiddleware])

Use cases

Mutating the context in your middleware

import { withMiddleware, Next } from 'az-func-middleware'

const myMiddleware = async (context: Context, next: Next) => {
  context.res = {
    status: 401,
    body: { message: 'You do not have access' }
  }

  // call next depending on your use-case
  await next(context)
}

export default withMiddleware(httpTrigger, [myMiddleware])

Make sure your function does not execute when the response is already set.

const httpTrigger: AzureFunction = async function (context: Context): Promise<void> {
  if(context.res) return
}

export default withMiddleware(httpTrigger, [myMiddleware])