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

next-middlewares

v1.0.0

Published

A library that can use multiple middleware in Next

Downloads

8

Readme

Next Middlewares

publish MIT License npm npm dependents npm downloads

This is a library that can use multiple middlewares in Next.

Introduction

Next's middleware cannot be configured with multiple middlewares. To solve this problem, we provide a library to allow Next to support multiple middlewares.

Supported Versions

next-middlewares is tested with:

  • next: 13.0.0 and above

Installation

First, install next-middlewares:

$ npm install next-middlewares

# OR

$ yarn add next-middlewares

# OR

$ pnpm install next-middlewares

Usage

The way to define middlewares is almost exactly the same as Next. For details, please refer to the Next document Middleware. The difference is that we only support config.match, other configurations will be ignored.

For example, you can create a new middlewares folder and create a new redirection middleware redirect.ts in it, the code is as follows

import { NextResponse } from 'next/server'
import type { NextRequest } from 'next/server'

export function middleware(request: NextRequest): Promise<NextResponse> {
  return NextResponse.redirect(new URL('/home', request.url))
}

export const config = {
  matcher: '/about',
};

Then, we can create a new middleware.ts file in the app or src or pages directory of the project according to Next's specifications. And reference our middlewares, use createMiddleware to combine them. Code show as below:

import { createMiddleware, config } from 'next-middlewares';

import * as RedirectMiddleware from './middlewares/redirect';
import * as RSSMiddleware from './middlewares/rss';

export const middleware = createMiddleware([RedirectMiddleware, RSSMiddleware]);

export { config };

That's all there is to it, your app will support multiple middlewares.

License

MIT