Update to Next 14 (and other dependencies) #46
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
images.domains is deprecated as of Next 14.
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.
Upgrade Next to v14.2.18, and @supabase/ssr to v0.5.2. Resolves npm audit yelling about vulnerabilities, as well as as potentially minor speed increases.
Ultimately may not have significant impact, but it will be easier to upgrade to Next 15 later. (I have not yet upgraded to Next 15 as it depends on React 19, which is currently still not stable.)
When testing, don't forget to do another
npm ci.If you need to go back to a different branch, or choose to not merge this branch, remember to nuke node_modules and reinstall. (Apologies for the inconvenience.)