Can't get the experimental nodeMiddleware working

[pip8786]

Summary

I have it set up essentially the same way as this: #77807 (comment) and like in that post it still gives me the errors:

   - Experiments (use with caution):
     ✓ nodeMiddleware

 ✓ Starting...
 ○ Compiling middleware ...
 ✓ Compiled middleware in 550ms
 ✓ Ready in 1281ms
 ⨯ Error: The edge runtime does not support Node.js 'crypto' module.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime

Any ideas?

Additional information

No response

Example

No response

[pip8786]

@jolic Were you able to resolve it? I can't respond to the issue linked above since it was closed. Thanks!

[pip8786]

Yeah... let's try to follow the import path. This is likely an issue when analyzing the code, so to speak, cuz using crypto directly on the middleware works fine

Did you need me to follow up on this or is this something you can do on your side with the repo provided?

[icyJoseph]

Alright, got a work-around for now. Could you try:

// middleware.ts
// export { auth } from './auth';
import { auth } from './auth';

export const middleware = auth;

export const config = {
  runtime: "nodejs",
};

[pip8786]

So changing the full middleware.ts file to this?

import { auth } from "./auth";

export const middleware = auth;

export { auth } from "./auth";

export const config = {
  runtime: "nodejs",
};

I'm still getting the same errors as before doing that.

However if I do just

import { auth } from "./auth";

export const middleware = auth;

//export { auth } from "./auth"; REMOVE THIS LINE

export const config = {
  runtime: "nodejs",
};

it gets passed the errors. The login itself doesn't work yet but that's probably a separate issue that I can look into.

[icyJoseph]

Yes, sorry it was late and I meant to copy the config, and pasted the auth line again... my bad. I fixed the snippet now.

but yeah, the issue seems to be, the export { auth as middleware } from './auth' bit ~

[icyJoseph]

Opting out from --turbopack also fixes the issue right?

[ebellumat]

I have the same issue here, i'm using "next": "15.3.4",

[icyJoseph]

As of today, you still need to use next@canary to use nodeMiddleware.

[icyJoseph]

With 15.5 nodeMiddleware is now stable! https://nextjs.org/blog/next-15-5#nodejs-middleware-stable