feat(core): detect NEXTAUTH_SECRET
#3783
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since v4, we have made providing a secret mandatory in production. The
NextAuth
configuration (in[...nextauth].js
) required either the top-levelsecret
orjwt.secret
values to be set, otherwise an error is thrown. https://next-auth.js.org/errors#no_secretTo make this configuration easier (which ties in with #3657), we are going to detect if you set a
NEXTAUTH_SECRET
variable automatically, so it is less likely that you end up with the above error.Reasoning 馃挕
Checklist 馃Б
Affected issues 馃師