feat: migrate to v4

[ndom91]

Migrated everything that needs changed so far.

I did, however, run into one console error regarding jwt that I wasn't sure about. Maybe I forgot to migrate something?

For example, on the "API" page of the example app, which is supposed to print the current session and jwt info, I get the following in my node console:

event - build page: /api/examples/jwt
TypeError [ERR_INVALID_ARG_TYPE]: The "key" argument must be of type string or an instance of SecretKeyObject, ArrayBuffer, TypedArray, DataView, or Buffer. Received undefined
    at Object.hkdfSync (node:internal/crypto/hkdf:134:7)
    at hkdf (/opt/ndomino/next-auth-typescript-example/node_modules/next-auth/dist/lib/jwt.js:127:40)
    at getDerivedSigningKey (/opt/ndomino/next-auth-typescript-example/node_modules/next-auth/dist/lib/jwt.js:143:18)
    at decode (/opt/ndomino/next-auth-typescript-example/node_modules/next-auth/dist/lib/jwt.js:81:96)
    at getToken (/opt/ndomino/next-auth-typescript-example/node_modules/next-auth/dist/lib/jwt.js:109:12)
    at jwt (webpack-internal:///./pages/api/examples/jwt.ts:11:78)
    at Object.apiResolver (/opt/ndomino/next-auth-typescript-example/node_modules/next/dist/server/api-utils.js:101:15)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
    at async DevServer.handleApiRequest (/opt/ndomino/next-auth-typescript-example/node_modules/next/dist/server/next-server.js:760:9)
    at async Object.fn (/opt/ndomino/next-auth-typescript-example/node_modules/next/dist/server/next-server.js:651:37) {
  code: 'ERR_INVALID_ARG_TYPE'
}

On both the normal and typescript example apps btw.

Any idea whats going on there? Did I miss something in terms of the migration?

Obviously there will probably be a few more small things to change before this is really up to snuff for v4.0.0 (final), but hopefully this takes care of most of the work and then we can merge this PR whenever the day comes tada

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

next-auth-example – ./

🔍 Inspect: https://vercel.com/nextauthjs/next-auth-example/BX7KU5aofL8TLpuskCuYZKJM3ETZ
✅ Preview: https://next-auth-example-git-ndom91-update-v4-nextauthjs.vercel.app

[ndom91]

Same deal here, I updated next-auth in this PR to 4.0.0-next.24. Also the jwt error seemed to be resolved once I explicitly set the same secret in the config under both config.secret and config.jwt.secret.

Also in this example in /pages/api/examples/jwt.js it was having trouble with getToken from next-auth/jwt. It needed to be explicitly imported as a named import apparently.

[motleydev]

I attempted to use this PR and defining an email provider as well as installing nodemailer throws an "adapter undefined" error.

Error: [next-auth][error][EMAIL_REQUIRES_ADAPTER_ERROR]

Deps:

"dependencies": {
    "next": "11.1.2",
    "next-auth": "^4.0.0-beta.2",
    "nodemailer": "^6.6.3",
    "pg": "^8.7.1",
    "react": "17.0.2",
    "react-dom": "17.0.2"
  },

Provider Config:

providers: [
    EmailProvider({
      server: process.env.EMAIL_SERVER,
      from: process.env.EMAIL_FROM,
    }),
  ],

I'm using a mailtrap smtp connection string. FWIW.

[balazsorban44]

as the message says, you'll need an adapter. 😅

https://next-auth.js.org/adapters/overview

@ndom91 we could explain it a bit better in:
https://next-auth.js.org/errors#email_requires_adapter_error

[motleydev]

as the message says, you'll need an adapter. 😅

https://next-auth.js.org/adapters/overview

@ndom91 we could explain it a bit better in:
https://next-auth.js.org/errors#email_requires_adapter_error

Hah, I did get THAT far. 😂 I installed nodemailer like mentioned above, which is what the docs indicated as the only required "adapter" needed - am I missing something additional to that? Sorry for the noob Q - hopefully this will help clarify some extra points for those that come after. :)

[balazsorban44]

nodemailer is not an adapter, it is a library that helps you sending emails. an adapter is a way for us to save data in a database. which is a requirement for the Email provider. see the docs link in my previous reply

[balazsorban44]

Could you update this to use beta.7 To be ready for merge?

[ndom91]

@balazsorban44 updated the PR to beta.7 👍

[ndom91]

@balazsorban44 since updating to beta.7 this is seemingly having those typescript issues resolving next-auth/react again at build time on vercel (https://vercel.com/nextauthjs/next-auth-example/3PyFJEmnfyyF5eMZyjjG93jCUHXj)

[balazsorban44]

we will need to comment out the email adapter

[ndom91]

we will need to comment out the email adapter

Okay, done 👍