getProviders is not available in v5 beta 3 #9209
Replies: 3 comments 1 reply
-
Hello, guys! I just hit the same roadblock with v5 beta.3, and that missing getProviders. Is there any estimate on when this issue will be solved? |
Beta Was this translation helpful? Give feedback.
-
It appears that |
Beta Was this translation helpful? Give feedback.
-
Thanks, @Evanion. I have been using @ts-ignore. I have registered an issue. The authors of next-auth said they will remove getProviders from the client side and turn it into a Server Component instead. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
Non-Goals
No response
Background
Apologies if I've overlooked something, but I've been diving into the v5 beta.3 release, and it seems like the getProviders functionality is no longer available. This feature was very useful for login experience to fit various scenarios, and its absence in the latest beta is posing some challenges. If this functionality is indeed deprecated or replaced in v5, it might disrupt several existing scenarios and make the upgrade process more intricate.
Please let me know if there is another way to the the object that have all providers available for client side.
Previously, I used the following approach in Login.tsx:
Login.tsx:
The error occurs on the line: "import { getProviders, signIn } from 'next-auth/react'"
Module '"next-auth/react"' has no exported member 'getProviders'
Proposal
Get back the working code of v4
Beta Was this translation helpful? Give feedback.
All reactions