#221 Upgrade NextJS #226
Merged
#221 Upgrade NextJS #226
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
nevendyulgerov
added
the
Type: Chore
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
4 tasks
brunomenezes
approved these changes
Aug 7, 2024
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.
I upgraded NextJS to its latest version and tested for regressions. I didn't find any issues.
I did notice however some performance improvements in terms of the dev server speed - quicker initial build times and faster HMR. Also, turbopack seems to be in stable state now, so maybe we can start using it with
next dev --turbo.