Middleware does not run when concurrentFeatures is enabled

[saurabhguptarock]

What version of Next.js are you using?

12.0.5-canary.9

What version of Node.js are you using?

14.18.1

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

Vercel

Describe the Bug

Middleware does not run and redirects user.

Expected Behavior

Middleware should redirect to login page.

To Reproduce

module.exports = {
  images: {
    deviceSizes: [640],
    domains: ["avatars.dicebear.com"],
    formats: ["image/avif", "image/webp"],
  },
  createRoot: true,
  swcMinify: false,
  experimental: {
    reactRoot: true,
    concurrentFeatures: true,
    serverComponents: true,
  },
};

_middleware.tsx

import type { NextRequest } from "next/server";
import { NextResponse } from "next/server";

export const middleware = (req: NextRequest) => {
  const cookie = req.cookies["auth"];

  if (!cookie) {
    return NextResponse.redirect("/login");
  }
};

[KlotzJesse]

Just won't work in the main ./pages folder. When added on an api route or /api directly, or in an sub-folder of ./pages it runs.

e.g.
./pages/_middleware.ts wont work
./pages/app/_middleware.ts will work
./pages/api/_middleware.ts will work

Also in 12.0.5-canary.10

[saurabhguptarock]

Just won't work in the main ./pages folder. When added on an api route or /api directly, or in an sub-folder of ./pages it runs.

e.g. ./pages/_middleware.ts wont work ./pages/app/_middleware.ts will work ./pages/api/_middleware.ts will work

Also in 12.0.5-canary.10

I have my middleware in sub folder but still not running

[huozhi]

Resolved with next 12.2

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.