Have can I get a NextRequest in middleware

[ryanwooa]

I add auth0 v4 in my middleware.ts
and use auth0.middleware(request) to handle /auth/login
This is what I learned from Auth0 official Docs.

It worked on local

The question is on the Vercel, if you run middleware in App routes, not page routes, you will only get Request, not NextRequest. As a result, the Auth0 midddleware can't handle with Request, because it is handling with Request.nextUrl field which is not included in Request

Is there any way to avoid this.
Or should I give up with this auth0.middleware

[icyJoseph]

if you run middleware in App routes, not page routes, you will only get Request, not NextRequest. As a result

How do you mean? Middleware is called with NextRequest, which extends Request. So if a function expects Request as a parameter, you can still pass NextRequest, but not vice-versa.

• https://nextjs.org/docs/app/api-reference/file-conventions/middleware

// middleware.ts
import { NextResponse, NextRequest } from 'next/server'

export function middleware(request: NextRequest) {
  console.log(request.nextUrl) // should print an object
  return NextResponse.redirect(new URL('/home', request.url))
}
 

[icyJoseph]

🤔 Idk, I mean, we have done a fair bit of troubleshooting. If it doesn't bother you so much please do.

I deployed a project with a simple middleware and I see nextUrl.

[ryanwooa]

which version of Nextjs, V15? , I m think update my nextjs from v14 to v15

[icyJoseph]

Yeah I used 15, but 14 should work fine though - but if you can upgrade to 15 without much hassle, go for it. Be careful with the async APIs breaking change. https://nextjs.org/docs/app/guides/upgrading/version-15#async-request-apis-breaking-change

[ryanwooa]

Hi, after upgrading to Next.js 15, I kept encountering issues. However, with more detailed error logs, I eventually discovered that the root cause was that I had placed all the Auth0 environment variables in the .env file. During middleware execution, those variables couldn’t be accessed—I wasn’t sure why. Once I moved all the environment variables into Vercel’s environment settings, everything worked fine. I even tested an older branch (based on Next.js 14), and once I configured the environment variables in Vercel instead of relying on the .env file, it also worked as expected.

Previously, I wasn't using middleware, and storing the environment variables in .env worked without issue.

I also noticed that when printing request directly, nextUrl wasn’t visible. But when printing request.nextUrl, it was indeed accessible. I had been mistakenly only logging request, so I didn’t realize that nextUrl was available. In fact, I had used request.nextUrl.pathname in some condition checks before, and those had worked—meaning nextUrl was accessible all along. So in the end, there actually wasn’t any problem.

XD

[icyJoseph]

I knew it! haha this was wayyy to puzzling - such is the software developer life

If you don't mind, maybe just choose my very first comment as answer, and close the issue :)