Typescript 使用NextJS中间件重定向，特定页面除外

您可以try 并测试一种更简洁的方法来实现您的目标，同时仍然将逻辑保持在middleware以内:使用正则表达式(Regex)来测试请求的路径名.

export function middleware(request: NextRequest) {
    const url = request.nextUrl.clone();
    const excludedPaths = /^(\/signup|\/_next|\/_axiom|\/_api|.*\..*)/;
    if (!excludedPaths.test(url.pathname)) {
        url.pathname = '/signup';
        return NextResponse.redirect(url);
    }
}

This uses a regular expression excludedPaths, created to match the paths that should be excluded from redirection.
The test() method is used to check if url.pathname matches any of the excluded paths.
If url.pathname does not match any of the excluded paths, it is redirected to /signup.

这种方法避免了冗长的一系列条件条件，应该会提供更紧凑的解决方案.

That being said, considering "How to use matcher in Next.js middleware", for Next.js version 12.2, the middleware.ts file should be placed in the project root, while for version 13.1.6, it should be placed in the src directory.
If you are using Next.js version 13.1.6 or a similar version, moving the middleware.ts file to the src directory as suggested might resolve the issue.

您可能需要调整matcher属性中的正则表达式，以确保它与您想要处理的路由正确匹配.

// File path: <project-root>/src/middleware.ts

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

export function middleware(request: NextRequest) {
    return NextResponse.redirect(new URL("/signup", request.url));
}

export const config = {
    matcher: new RegExp("/((?!signup|_axiom|_api|_next/static|_next/image).*)"),
};

这将把middleware.ts文件放在Next.js版本13.1.6的src目录中，并更新matcher属性以使用RegExp对象而不是字符串.