build: Next.js 16 with reactCompiler and cacheComponents #154
Conversation
This file contains hidden or 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
AdrianAndersen
added
the
Build
AdrianAndersen
force-pushed
the
perf-next-16
branch
from
b428bc6 to
0230a3e
Compare
Collaborator
Author
|
The CI build is failing due to: @mathiazom u 👨🏻🔧 ? |
AdrianAndersen
force-pushed
the
perf-next-16
branch
2 times, most recently
from
429039b to
b1f115d
Compare
Collaborator
Author
|
Up to date now 🤓 |
AdrianAndersen
force-pushed
the
perf-next-16
branch
from
b1f115d to
b3a16a1
Compare
Collaborator
Author
|
Now with the RSC security patch 👀 |
mathiazom
force-pushed
the
perf-next-16
branch
from
b3a16a1 to
8dc7e49
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Bumped Next.js to v16.
Also enabled React Compiler, Cache Components and added some Activities where we have used traditional conditional rendering.
For now, I have ignored most of the new eslint react hooks errors, since the useEffects in is a bit of a nightmare right now. The result is that the compiler will just opt of of the components that do not follow the rules. Therefore, this should not be a problem, but rather an area that we can iterate on so that the compiler can optimize more and more of the code.
This PR will make it easier to fix the useEffects later, since we can use React 19.2s new shiny useEventEffect 🤩