Credential Login Authorize Function Runs on Edge, somehow

[ArmanRahno]

I have a problem with the implementation of the middleware, I presume. In the beginning, I used Firestore with test rules. However, as I didn't know that the server shouldn't use the client SDKs, I tried to change it to admin SDKs and have even tried MongoDB. The problem is that I get the error below:

Error: The edge runtime does not support Node.js 'stream' module.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime
at (webpack-internal:///(middleware)/./node_modules/next/dist/esm/server/web/globals.js:33)
at Object.get (webpack-internal:///(middleware)/./node_modules/next/dist/esm/server/web/globals.js:33:19)
at eval (webpack-internal:///(middleware)/./node_modules/mongodb/lib/cursor/abstract_cursor.js:617:45)
at (middleware)/./node_modules/mongodb/lib/cursor/abstract_cursor.js (file:///Users/arman/Documents/Code/istut/istut-v2/.next/server/src/middleware.js:1152:1)
at webpack_require (file:///Users/arman/Documents/Code/istut/istut-v2/.next/server/edge-runtime-webpack.js:37:33)
at fn (file:///Users/arman/Documents/Code/istut/istut-v2/.next/server/edge-runtime-webpack.js:280:21)
at eval (webpack-internal:///(middleware)/./node_modules/mongodb/lib/cursor/aggregation_cursor.js:9:27)
at (middleware)/./node_modules/mongodb/lib/cursor/aggregation_cursor.js (file:///Users/arman/Documents/Code/istut/istut-v2/.next/server/src/middleware.js:1163:1)
at webpack_require (file:///Users/arman/Documents/Code/istut/istut-v2/.next/server/edge-runtime-webpack.js:37:33)
at fn (file:///Users/arman/Documents/Code/istut/istut-v2/.next/server/edge-runtime-webpack.js:280:21)
at eval (webpack-internal:///(middleware)/./node_modules/mongodb/lib/collection.js:10:30) {
middleware: true
}

And when I restart the development I get a ginormous amount of errors, all of which have the exact same message except their dependency names:

Module not found: Can't resolve 'dependencyname' in '/Users/arman/Documents/Code/istut/istut-v2/node_modules/mongodb/lib'

By the way, the code inside my credential login's authorize function is causing this. This is happening due to some kind of leakage of the auth.config or auth.ts files to the middleware, I assume.
I refactored my code such that it uses MongoDB, and the app doesn't have a single problem except when I add even the most simple console.log((await client.connect()).db("users").collection("users").find()); inside the authorize function.

Relevant Code

middleware.ts

import { NextResponse } from "next/server";
import authConfig from "./auth.config";
import NextAuth from "next-auth";

const { auth } = NextAuth(authConfig);

export default auth(req => {
// If route is admin and isLoggedIn has admin on it, permit access,

const { nextUrl } = req;

const isLoggedIn = !!req.auth;

if (nextUrl.pathname.startsWith("/api/auth")) {
	return null;
}

if (!isLoggedIn && !nextUrl.pathname.startsWith("/auth"))
	return NextResponse.redirect(new URL("/auth/login", nextUrl));

if (isLoggedIn && nextUrl.pathname.startsWith("/auth"))
	return NextResponse.redirect(new URL("/settings", nextUrl));

return null;

});

export const config = {
matcher: ["/((?!.+\.[\w]+$|_next|$|auth/new-verification).)", "/(api|trpc)(.)"]
};

auth.ts

import NextAuth, { Account } from "next-auth";
import authConfig from "./auth.config";
import { FirestoreAdapter } from "@auth/firebase-adapter";
import { accountsCol, app, db, usersCol } from "./lib/firebaseConfig";
import { doc, getDoc, getDocs, query, where, limit } from "firebase/firestore";
import { cert } from "firebase-admin/app";

export const {
handlers: { GET, POST },
auth,
signIn,
signOut
} = NextAuth({
session: { strategy: "jwt" },
...authConfig
});

auth.config.ts

import { NextAuthConfig } from "next-auth";

import Credentials from "next-auth/providers/credentials";
import { LoginSchema } from "./schemas/login";

import client from "./lib/client";

export default {
providers: [
Credentials({
async authorize(credentials) {
const validatedFields = LoginSchema.safeParse(credentials);

			console.log((await client.connect()).db("users").collection("users").find());

			return null;
		}
	})
],
pages: { signIn: "/auth/login", error: "/auth/error" }

} satisfies NextAuthConfig;

I would be more than willing to provide more information regarding the related files if need be.

Heaps of thanks ahead of time :)

[ArmanRahno]

Alright, found a workaround using the data api:
https://blog.stackademic.com/authentication-and-authorization-on-the-edge-with-auth-js-nextauth-5-and-mongodb-5903d7e95f99

[DavDeDev]

Hi Arman, could you please share your new authorize method for the Credentials provider? I tried to follow the same tutorial, but when I tried to build the app it still gives error because local MongoDB and mongoose cannot run on the edge :/
Thank you so much!