You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the improvement or update you wish to see?
The docs are missing information about the reasons for beta label of v5.
Is there any context that might help us understand?
The v5 npm package is marked as a beta release (next-auth@beta), but there is no clear explanation in the documentation about the reasons for this status (or at least I wasn’t able to find one).
Could you please add details regarding the beta label, specifically:
The reasons for the beta label
Whether there are potential security concerns or risks for production use
Any known significant limitations or planned updates
This information would help users make informed decisions about choosing v5 over v4. I’m hesitant to use a library marked as beta for such a critical aspect as security/authentication without complete information.
Thank you!
Does the docs page already exist? Please link to it.
No response
The text was updated successfully, but these errors were encountered:
kuchejak
added
the
triage
Unseen or unconfirmed by a maintainer yet. Provide extra information in the meantime.
label
Nov 5, 2024
What is the improvement or update you wish to see?
The docs are missing information about the reasons for beta label of v5.
Is there any context that might help us understand?
The v5 npm package is marked as a beta release (next-auth@beta), but there is no clear explanation in the documentation about the reasons for this status (or at least I wasn’t able to find one).
Could you please add details regarding the beta label, specifically:
This information would help users make informed decisions about choosing v5 over v4. I’m hesitant to use a library marked as beta for such a critical aspect as security/authentication without complete information.
Thank you!
Does the docs page already exist? Please link to it.
No response
The text was updated successfully, but these errors were encountered: