force the middleware to use Node.js runtime

[gestchild]

What does this change?

Force the middleware runtime to use Node.js so AsyncLocalStorage is available

I think this will fix the error we are having in the identity app currently on stage

Error: Invariant: AsyncLocalStorage accessed in runtime where it is not available

How to test

Deploy to stage and see if it works...

[Copilot]

Pull request overview

This PR attempts to resolve a Stage error in the identity app (“AsyncLocalStorage accessed in runtime where it is not available”) by forcing the Next.js middleware to run in the Node.js runtime so Node-only APIs are available.

Changes:

• Adds a Node.js runtime override for identity/webapp/middleware.ts.

Comments suppressed due to low confidence (1)

identity/webapp/middleware.ts:85

• export const runtime = 'nodejs' is not the documented/supported way to opt Middleware into the Node.js runtime in Next.js 15.x; runtime selection for middleware is expected to be set via the exported config object (e.g. export const config = { …, runtime: 'nodejs' }). As written, this may be ignored and you’ll still be running in the default Edge runtime, so the AsyncLocalStorage error would persist.

export const runtime = 'nodejs';