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

nitro-conditional-middleware

v0.1.3

Published

Tools for creating conditional middlewares for nitro

Downloads

310

Readme

nitro-conditional-middleware

Development

install

npm install

test

npm run test

lint

npm run lint:fix

build

npm run build

Documentation

A brief explanation on how middlewares in nitrojs work.

NitroJS provides as base for their middlewares H3 event handlers created by defineEventHandler.

Middlewares in the nitrojs framework are executed in every request.

Real life scenarios

In this diagram we display 3 different scenarios that our server needs to handle:

  • Open API requests
  • Authenticated API requests
  • HealthCheck Requests

Problem

Knowing that all events will pass through all middlewares, we need to plan the flow based on conditions that will run or skip these middlewares

Middleware diagrams

Skipping middlewares

With the constrain that the event flow will pass through all middleware event handlers, we needed a way to skip a middleware for some events that will go through the middleware pipeline based on a particular condition.

This library creates a way to pass a condition as parameter to create defineMiddlewareHandler functions with a run condition. This function has the same signature as as H3's defineEventHandler. Making it a 1:1 substitute.

type condition = (event: H3Event) => boolean

// This function would return a handler as H3's `defineEventHandler`
const defineMiddlewareHandler = createMiddlewareHandler(condition)

Creating and using multiple middlewareHandlers

// defineApiMiddleware.ts
import { createMiddlewareHandler } from 'nitro-conditional-middleware'

const apiV1MiddlewareHandler = createMiddlewareHandler((event) => {
  return event.path.includes('/api/v1/')
})

const apiV2ConditionFn = (event: H3Event) => boolean {
  return event.path.includes('/api/v2/')
}

const apiV2MiddlewareHandler = createMiddlewareHandler(apiV2ConditionFn)
// usage 1.my-first-middleware.ts
import { apiV1MiddlewareHandler } from './defineApiMiddleware'

const myFirstMiddleware = (event) => {
  console.log('myFirstMiddleware: This will only run in api/v1 endpoints')
}

export default apiV1MiddlewareHandler(myFirstMiddleware)
// usage 2.my-second-middleware.ts
import { apiV2MiddlewareHandler } from './defineApiMiddleware'

export default apiV2MiddlewareHandler((event) => {
  console.log('mySecondMiddleware: This will only run in api/v2 endpoints')
})