Auth.js V5 ready for production use in Nextjs applications?

[abhayc-main]

Is auth.js v5 ready for production use in NextJS apps? There are no widely reported known issues with using NextAuth.js version 5 in production. The package is considered production-ready and has been adopted by many users for their production applications
1
2. While some users have reported specific issues or challenges with the library, no critical issue would preclude its use in a production environment.

The docs still mention that they are in Beta and experimental. Is it worth switching?

[TimKieu]

I am also waiting for the production release v5.
So far, 2024.01.08, the V5 beta-4 still does not run smoothly on Edge runtime V8.

[abhayc-main]

you think its worth switching?

[TimKieu]

Yes, it is worth to switch whenever v5 production is ready. Then you can apply on Nextjs apps or others (Qwik) on both Vercel or Cloudflare flexibly.

[ahmad-punch]

Hey Guys, It's been some time. When should we expect this v5 to be production ready?

[Exp1ry]

Can we get an update? So many of us need an answer..

[VitaliyPotapov]

No answer is also an answer :(

[AliakseiPaseishviliSyntheticabio]

@balazsorban44, you are the creator of this repo, any comments on this?

[Exp1ry]

@balazsorban44 Re-tagging you for a reply.

[pricciafelio]

@balazsorban44 Re-tagging you for a reply.

[max-degterev]

@balazsorban44 @ThangHuuVu seriously though guys, we are all appreciative for your past efforts but it's clear the spark isn't there anymore. Sponsor money are nice but maybe archive the repo and put a disclaimer that it's no longer maintained. People deserve to be able to move on.

[falcowinkler]

sorry for the radio silence on this. we will get back to you soon.

[VitaliyPotapov]

From this post:

Auth.js, formerly known as NextAuth.js, is now being maintained and overseen by Better Auth team

[max-degterev]

You mean team that committed "make me admin === true": https://www.reddit.com/r/javascript/s/5I64e6T0uz

I think with next.js 16 release we've reached the end of the road here.

[ragnarok22]

This was a great project 😔

[ndom91]

Chiming in here so that everyone who's subscribed and hasn't been following updates knows - Auth.js is being maintained by the better-auth team now and we recommend migrating there when/if time allows.

We won't be doing any new feature work at Auth.js, but any critical bugs or security issues will still be patched for a while.

[Exp1ry]

Will Authjs V5 be stepping out of beta atleast?

[Exp1ry]

@ndom91 Hi, I currently have a live platform with hundreds of users. We use AuthJS v5. Could I get a confirmation on whether AuthJS will be stepping out of beta? If not, then we might as well migrate to better-auth.

[ragnarok22]

@Exp1ry my advice: migrate to another library. I'm searching for one that accepts a backend that is not written in JS.

[max-degterev]

guys just roll your own auth. Every meme auth library out there either has downtime (clerk) or has serious security issues (better auth)

this is your wake up call to stop using vibe coded bs for critical system functions

[Exp1ry]

That's the thing, thats why AuthJS was so perfect.. To me, it was just the top layer of enterprise-grade cookie storage/management. I just used it as the Authentication layer.

The problem with better-auth is that it forces you to intertwine your authorization logic with their pre-written system. For example, I hate how you need to use their 2FA / verification setup. With AuthJS, you pass fields into the session, and from there you can write your own logic to determine whether a user is really authorized or not (even though they are signed in already).

Sad day for us..