Replacing NextAuth with Clerk in T3
I'm currently developing a web app with the T3 stack, and my client requires authentication via email/password. I've heard NextAuth has limitations regarding the matter, and since I've only used it for logging in with social providers:
- Would it be worth replacing NextAuth with Clerk? What are your thoughts and experience?
- Has anyone done or written a guide about said replacement? I'm in the middle of development and I'm not sure if the switch's going to take a lot of time.
Thanks!
2 Replies
Hey man, ive used clerk in two t3 apps now and the setup is almost a like-for-like swap. Essentially replacing the NextAuth calls with clerk equivalents.
heres a blog post from the clerk team: https://clerk.com/blog/clerk-t3-turbo
Clerk
Clerk and Create T3 Turbo
This guide shows you how to integrate Clerk into T3-Turbo so you can have user management for everyone.
It will be a lot easier to add password authentication to nextauth.