如何解析 next-auth 中的 'getUserByAccount is not a function'？

Question

我已经将 Nextjs 更新到它的最新版本，并且还更新了文档指定的 next-auth 和 prisma 适配器。

但是，当我尝试在应用程序中使用 signIn 进行身份验证时，最新更新出现以下错误：

[next-auth][error][OAUTH_CALLBACK_HANDLER_ERROR] 
https://next-auth.js.org/errors#oauth_callback_handler_error getUserByAccount is not a function {
  message: 'getUserByAccount is not a function',
  stack: 'TypeError: getUserByAccount is not a function\n' +
    '    at Object.callback (/home/.../node_modules/next-auth/core/routes/callback.js:81:39)\n' +
    '    at runMicrotasks (<anonymous>)\n' +
    '    at processTicksAndRejections (internal/process/task_queues.js:95:5)\n' +
    '    at async NextAuthHandler (/home/.../node_modules/next-auth/core/index.js:103:28)\n' +
    '    at async NextAuthNextHandler (/home/.../node_modules/next-auth/next/index.js:40:7)\n' +
    '    at async [...]/node_modules/next-auth/next/index.js:80:32\n' +
    '    at async Object.apiResolver (/home/.../node_modules/next/dist/server/api-utils.js:102:9)\n' +
    '    at async DevServer.handleApiRequest (/home/.../node_modules/next/dist/server/next-server.js:1014:9)\n' +
    '    at async Object.fn (/home/.../node_modules/next/dist/server/next-server.js:901:37)\n' +
    '    at async Router.execute (/home/.../node_modules/next/dist/server/router.js:210:32)',
  name: 'TypeError'
}

是我做错了什么，还是我遗漏了不兼容的地方？

相关package.json:

...
    "@next-auth/prisma-adapter": "^0.5.2-next.19",
    "next": "^12.0.3",
    "next-auth": "4.0.0-beta.6",
    "prisma": "^3.4.1",
...

[...nextauth].ts:

import NextAuth from 'next-auth';
import CognitoProvider from 'next-auth/providers/cognito';
import { PrismaAdapter } from '@next-auth/prisma-adapter';
import { PrismaClient } from '@prisma/client';

const prisma = new PrismaClient();

export default NextAuth({
  adapter: PrismaAdapter(prisma),
  providers: [
    CognitoProvider({
      clientId: process.env.COGNITO_CLIENT_ID,
      clientSecret: process.env.COGNITO_CLIENT_SECRET,
      issuer: process.env.COGNITO_ISSUER,
    }),
  ],

  callbacks: {
    async session({ session, user }) {
      session.userId = user.id;
      session.role = user.role;
      return Promise.resolve(session);
    },
  },
});

Answer 1

在 NextAuth.JS 4.0 中，“Prisma 模式”略有变化。

来自upgrade guide：

created_at/createdAt and updated_at/updatedAt fields are removed from all Models.

user_id/userId consistently named userId.

compound_id/compoundId is removed from Account.

access_token/accessToken is removed from Session.

email_verified/emailVerified on User is consistently named email_verified.

provider_id/providerId renamed to provider on Account

provider_type/providerType renamed to type on Account

provider_account_id/providerAccountId on Account is consistently named providerAccountId

access_token_expires/accessTokenExpires on Account renamed to expires_in

New fields on Account: expires_at, token_type, scope, id_token, session_state

verification_requests table has been renamed to verification_tokens

在以下位置完成新架构： https://next-auth.js.org/adapters/prisma

Answer 2

问题终于解决了。由于next-auth已经迁移到monorepo，更新包不够，需要先卸载再安装。

运行:

npm uninstall next-auth @next-auth/prisma-adapter

然后：

npm install @next-auth/prisma-adapter

这帮我修好了。

如何解析 next-auth 中的 'getUserByAccount is not a function'？

How to resolve 'getUserByAccount is not a function' in next-auth?

next.js

prisma

next-auth