withMiddlewareAuthRequired - A Node.js API is used which is not supported in the Edge Runtime.

[TrevorThomp]

Checklist

• The issue can be reproduced in the sample app (or N/A).
• I have looked into the README and have not found a suitable solution or answer.
• I have looked into the examples and have not found a suitable solution or answer.
• I have looked into the API documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

I swapped the usage of withPageAuthRequired and withApiAuthRequired with withMiddlewareAuthRequired and when I run next build I'm seeing the following error that fails to build my containers in GCP.

./node_modules/next/dist/server/web/spec-extension/image-response.js
A Node.js API is used (process.turbopack at line: 47) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
 ./node_modules/next/dist/server/web/spec-extension/image-response.js
./node_modules/next/server.js
./node_modules/@auth0/nextjs-auth0/dist/helpers/with-middleware-auth-required.js
./node_modules/@auth0/nextjs-auth0/dist/edge.js

I wasn't noticing this error previously, but recently it has been consistent in each build. I swapped back to using withPageAuthRequired and withApiAuthRequired and also removed withMiddlewareAuthRequired which resolved the errors.

I used the same example as in the docs without any customization so not sure what could cause this to throw. I'm not using Edge API's in my application and they are all standard Node API's.

import { withMiddlewareAuthRequired } from '@auth0/nextjs-auth0/edge';

export default withMiddlewareAuthRequired();

I haven't been able to find anyone else having this same issue, so I've been at a loss. Any insight on this would be appreciated.

Reproduction

1. Follow doc usage of using withMiddlewareAuthRequired in the middleware.ts file
2. Run yarn build

SDK version

2.4

Next.js version

13.3

Node.js version

19

[adamjmcgrath]

Hi @TrevorThomp - thanks for raising this

I'm not able to reproduce this when running build for the example app, which has a similar middleware function https://github.com/auth0/nextjs-auth0/blob/main/examples/kitchen-sink-example/middleware.ts

Are you able to reproduce this locally and can you share a repo that demonstrates the issue?

[Charlie-Boyer]

I can confirm I have the same exact warning since updated to next 13.3, using withMiddlewareAuthRequired

[TrevorThomp]

@adamjmcgrath I will work on getting a reproducible example to you. For what it's worth, the file that is throwing this error is a recent change in the last 13.3 release of Next as @Charlie-Boyer pointed out.

vercel/next.js#47715
vercel/next.js@d71cbe9#diff-88cc5222d0ce7e563716eee434a1045d101b0043afd2450d66c9eb1ca4ac5cbb

[TrevorThomp]

@adamjmcgrath I was able to create an example repro that is throwing the error consistently.

1. Install dependencies
2. Run yarn:build and/or yarn docker:build - Sometimes it won't throw, so delete the .next folder and build again if not.

https://github.com/TrevorThomp/nextjs-auth-repro

[adamjmcgrath]

Thanks for sharing that repo @TrevorThomp

I'm still seeing the same warning if I change your middleware function to use next-auth

// middleware.ts
export { default } from "next-auth/middleware";

./node_modules/next/dist/server/web/spec-extension/image-response.js
A Node.js API is used (process.turbopack at line: 47) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/next/dist/server/web/spec-extension/image-response.js
./node_modules/next/server.js
./node_modules/next-auth/next/middleware.js
./node_modules/next-auth/middleware.js

So my guess is that this is an issue with next

[TrevorThomp]

Okay thanks for taking a look @adamjmcgrath. I will raise this issue with Next and see how this can get resolved. Feel free to close this issue in the interim as the way around it currently is to avoid using Next middleware...

For anyone else wanting to track the issue I'm raising it will be linked below.
vercel/next.js#48302

[adamjmcgrath]

ok, thanks @TrevorThomp - will keep an eye on that issue you raised and reopen this if anything is needed from our end

[semy]

I have the same error with next-auth