update @types/react version in examples #57259
Merged
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
HanCiHu
requested review from
timneutkens,
ijjk,
shuding,
styfle,
huozhi,
ztanner and
a team
as code owners
HanCiHu
requested review from
manovotny and
delbaoliveira
and removed request for
a team
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What?
When I ran
npx create-next-app --example with-turbopackand installed dependencies usingyarn, I found an typescript error('SomeComponent' cannot be used as a JSX component.).and I realized that the bug is due to the version of @types/react(18.0.x).
you can check this issue on here too.
Why?
It seems that there is an error occurring in the @types/react version 18.0.x.
How?
It would be good to change the @types/react version to 18.2.8 in the next.js examples.
I think this change will resolve this issue
NestJS documentation also states to upgrade the version.