Ali Raza Khalid
Ali Raza Khalid
ok waiting for the feature to be implemented
I think I have a fix of just signing in and handling an error if the password is incorrect. Instead of using signIn() function from the @/auth.js file we can...
Ok I do understand that. So we can wait until the new release makes a fix ?
What if we can customize the authorize() function to return custom errors like this https://github.com/nextauthjs/next-auth/pull/9871 And here https://github.com/nextauthjs/next-auth/issues/9099
@Qodestackr I would like to point out that wrapping your app directly with sessionprovider doesnot work instead import it in a client component and then wrap that component around your...
First thing first why did you write "use server" on the server component By default it was server component by marking you have made it a server action that works...
```const session = getServerSession(); ``` In a client marked component ? @Qodestackr
I tried cloning and running the repository but it does not seen to work even after installing all the modules. ```$ npm run dev``` > [email protected] dev > next dev...
I have myself implemented basic authentication using authjs and mongo db along with credentials and oauth providers and also implemented basic stripe payment . Take a look at the repository...
Also the official documentation suggests to create the auth.js file in the root of the directory. [Docs](https://authjs.dev/getting-started/installation?framework=next.js)