`getSession` fails during build when used in middleware

Environment

react 17.0.2 next-auth 4.3.3 next 12.1.5

Reproduction URL

N/A

Describe the issue

getSession does not work in nextjs middlewares. Or rather, it works during development but fails when trying to build the project, with the following trace:

./node_modules/@babel/runtime/helpers/isNativeFunction.js
Dynamic Code Evaluation (e. g. 'eval', 'new Function') not allowed in Middleware pages/planning/_middleware

Import trace for requested module:
./node_modules/@babel/runtime/helpers/wrapNativeSuper.js
./node_modules/next-auth/core/errors.js
./node_modules/next-auth/lib/logger.js
./node_modules/next-auth/react/index.js
./src/server/auth_middleware.ts
./src/pages/overview/_middleware.ts

This seems to be a “known” issue, #4302, but that issue was just closed out of hand, even though it was “supposed to work”.

According to the documentation, we are supposed to use withAuth but this requires the JWT session strategy, which I’m not using.

What is the recommended approach here?

How to reproduce

1. Create new next project with next-auth and session auth and any adapter
2. Try to use getSession in middlewares
3. Try to build the project

Expected behavior

It doesn’t fail to build.

[balazsorban44]

Sorry, the reason is that getSession is not compatible with the Edge Runtime, but we are working on it.

The reason is that some of the core relies in Node.js, plus there isn’t many Edge compatible database solutions yet, as far as I know.

This is briefly mentioned under caveats of the Middleware documentation.

https://next-auth.js.org/configuration/nextjs#caveats

[HenriqueRamos13]

So, for who is using a non-JWT strategy, we need just wait getSession get compatible with edge functions? Or have another way?