refactor: downgrade @types/react to a suitable version #211
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
WhiteMinds
requested review from
zhangyouxin,
Daryl-L,
Keith-CY and
PainterPuppets
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Keith-CY
approved these changes
Jan 17, 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.
Directly downgrading the type will trigger another issue, which was introduced from 8b5c2b0.
It seems that some misoperations were made to
yarn.lockduring themerge, causing subsequentyarn.lockto have problems. Therefore, there will be many changes toyarn.lockin this PR to fix yarn.lock to the correct path.