Is the authorize function run on the edge in the Credentials provider?

[TheAndry]

My question is that is Credential authorize method run on edge mode that this happens?

I try to get user from db in authorize function in Credentials provider and I get this error. I know this comes from knex and i tried to use authjs-knexjs-adapter(https://github.com/travishorn/authjs-knexjs-adapter) package for adapter (I want to use MySQL db).
But i want to understand why I get this error? Does it mean that authorize function is ran on the edge? Or I can somehow still query the db in authorize function?

⨯ Error: The edge runtime does not support Node.js 'tty' module.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime
    at <unknown> (webpack-internal:///(middleware)/./node_modules/next/dist/esm/server/web/globals.js:43)
    at Object.apply (webpack-internal:///(middleware)/./node_modules/next/dist/esm/server/web/globals.js:43:19)
    at eval (webpack-internal:///(middleware)/./node_modules/colorette/index.cjs:39:61)
    at (middleware)/./node_modules/colorette/index.cjs (file:///Users/andrykore/Projects/seiresearch/Frontend/portal/.next/server/src/middleware.js:4942:1)
    at __webpack_require__ (file:///Users/andrykore/Projects/seiresearch/Frontend/portal/.next/server/edge-runtime-webpack.js:37:33)
    at fn (file:///Users/andrykore/Projects/seiresearch/Frontend/portal/.next/server/edge-runtime-webpack.js:285:21)
    at eval (webpack-internal:///(middleware)/./node_modules/knex/lib/logger.js:1:15)
    at (middleware)/./node_modules/knex/lib/logger.js (file:///Users/andrykore/Projects/seiresearch/Frontend/portal/.next/server/src/middleware.js:1230:1)
    at __webpack_require__ (file:///Users/andrykore/Projects/seiresearch/Frontend/portal/.next/server/edge-runtime-webpack.js:37:33)
    at fn (file:///Users/andrykore/Projects/seiresearch/Frontend/portal/.next/server/edge-runtime-webpack.js:285:21)
    at eval (webpack-internal:///(middleware)/./node_modules/knex/lib/client.js:29:16)
 ⚠ Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/messages/fast-refresh-reload
 GET /_next/static/webpack/103a562b553de19f.webpack.hot-update.json 404 in 2103ms

My auth.config.ts

import { NextAuthConfig } from "next-auth";
import Credentials from "@auth/core/providers/credentials";
import { LoginSchema } from "@/schemas/auth";
import bcrypt from "bcryptjs";
import { getUserByEmail } from "@/data/getUserByEmail";

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

        if (validatedFields.success) {
          const { email, password } = validatedFields.data;

          const user = await getUserByEmail(email);

          if (!user || !user.password) return null;

          const passwordsMatch = await bcrypt.compare(password, user.password);

          if (passwordsMatch) return user;
        }
        if (!validatedFields) {
          return null;
        }

        return;
      },
    }),
  ],
} satisfies NextAuthConfig;

My getUserByEmail.ts

import { db } from "@/lib/db";

export const getUserByEmail = async (email: string) => {
  try {
    return await db("user").where("email", email).first();
  } catch {
    return null;
  }
};

My db.ts

import knex from "knex";

export const db = knex({
  client: "mysql2",
  connection: {
    host: process.env.DB_HOST,
    port: parseInt(process.env.DB_PORT ?? "3306", 10),
    user: process.env.DB_USER,
    password: process.env.DB_PASSWORD,
    database: process.env.DB_DATABASE,
    insecureAuth: true,
  },
});

My auth.ts

import NextAuth from "next-auth";

import authConfig from "@/auth.config";
import { db } from "@/lib/db";
import { KnexAdapter } from "authjs-knexjs-adapter";

export const { handlers, signIn, signOut, auth } = NextAuth({
  adapter: KnexAdapter(db),
  session: {
    strategy: "jwt",
    maxAge: 30 * 24 * 60 * 60, // 30 days
  },
  ...authConfig,
});

My route.ts

import { handlers } from "@/auth";
export const { GET, POST } = handlers;

[k-taro56]

This message is generated by next dev, so I don't know what line of code is preventing it from working on edge.
Can you give me the full error message using next build?

However, I think it is probably caused by the adapter (KnexAdapter).
Knex may not support working with Edge at all, and it may not just be an adapter issue.
See also: https://authjs.dev/guides/edge-compatibility#database-adapters

[TheAndry]

But when I remove line const user = await getUserByEmail(email); it starts working.

I'm still not sure that KnexAdapter causes it and also the error shows that it comes from knex and from my db.ts file.
Thaks to this error I can see that the authorize method is imported to middleware.ts and as I read that middleware is Edge Runtime.

But how could i fix this?

Error when using next build

andry@Andrys-MacBook-Pro portal % yarn build
yarn run v1.22.22
$ next build
  ▲ Next.js 14.2.5
  - Environments: .env.local

   Creating an optimized production build ...
Failed to compile.

./src/lib/db.ts
Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime 
Learn More: https://nextjs.org/docs/messages/edge-dynamic-code-evaluation

The error was caused by importing 'knex/knex.js' in './src/lib/db.ts'.

Import trace for requested module:
  ./src/lib/db.ts
  ./src/data/user.ts
  ./src/auth.config.ts
  ./src/middleware.ts


> Build failed because of webpack errors
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.