Use next auth #1
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mystical cache miss upon visiting the page, will need to investigate later.
|
Deploy preview for alto ready! ✅ Preview Built with commit 25344d3. |
…e using session Fetches from POST handlers (the auth api route) and dynamic pages (the `/profile` page, because of `getServerSession()`) are not deduped. See vercel/next.js#52077 (comment)
|
Superseded by backend usage of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently struggles with weird cache misses from certain pages, and Next Auth might be a contributing factor to the newfound slowness of the dev server (and occasional out-of-memory warnings).
Might be nice to test in a prod-like setting on a preview URL to see if issues are mostly contained to development.