This repository has been archived by the owner on Jun 18, 2024. It is now read-only.
NextJS 13 upgrade #229
Open
NextJS 13 upgrade #229
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
kilemensi
approved these changes
Jul 21, 2023
| @@ -18,17 +18,23 @@ const Connector = () => { | |||
| ?.getBoundingClientRect(); | |||
|
|
|||
| if (firstElement && secondElement) { | |||
| // eslint-disable-next-line no-unsafe-optional-chaining | |||
There was a problem hiding this comment.
No easy way to fix these? Lots of disabling.
There was a problem hiding this comment.
Let me look at fixing it.
Co-authored-by: Clemence Kyara <[email protected]>
Yes. We will close it if it is ok. |
5 tasks
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.
Description
This PR updates the project to use NextJS 13.
Type of change
Checklist: