Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[React] Migration to React Version-18 #5732

Closed
wants to merge 9 commits into from

Conversation

Aviral0702
Copy link
Contributor

Description
This pull request upgrades the Layer5 website to React 18.
This PR fixes #

Notes for Reviewers

Signed commits

  • Yes, I signed my commits.

@leecalcote
Copy link
Member

Is React 18 required by Gatsby 5?

@leecalcote
Copy link
Member

@vishalvivekm @dottharun @sudhanshutech our focus should be on reviewing, updating, and merging @randychilau's most excellent work in this PR - #4646

Signed-off-by: Aviral Asthana <[email protected]>
@Aviral0702
Copy link
Contributor Author

Is React 18 required by Gatsby 5?

Yes, React 18 is required for migrating to Gatsby V5.

@l5io
Copy link
Contributor

l5io commented Jul 26, 2024

🚀 Preview for commit 8bc24cf at: https://66a40f0d07f56f50ab6b33d1--layer5.netlify.app

@l5io
Copy link
Contributor

l5io commented Jul 26, 2024

🚀 Preview for commit 8ab7724 at: https://66a413b79f41aa633b2496b1--layer5.netlify.app

@leecalcote
Copy link
Member

Is React 18 required by Gatsby 5?

Yes, React 18 is required for migrating to Gatsby V5.

Thank you for confirming. Please verify that this package supports React 18, too - https://github.com/layer5labs/meshery-extensions-packages/tree/master/meshery-design-embed

@Aviral0702
Copy link
Contributor Author

Is React 18 required by Gatsby 5?

Yes, React 18 is required for migrating to Gatsby V5.

Thank you for confirming. Please verify that this package supports React 18, too - https://github.com/layer5labs/meshery-extensions-packages/tree/master/meshery-design-embed

Currently, this package doesn't support React-18.

@@ -14,7 +14,7 @@ jobs:

- name: Install and Build 🔧
run: |
npm install
npm install --legacy-peer-deps
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reason?

@@ -17,7 +17,7 @@ jobs:

- name: Install and Build 🔧
run: |
npm install
npm install --legacy-peer-deps
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reason?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have included this because some packages do not support React 18. Therefore, during the installation process, it will skip those packages.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but is it safe?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not permanent change we will revert this when all the packages which currently do not support React - 18 are replaced. It is just to bypass those dependencies. I can build the site successfully after these changes. Also major dependency is Meshery-embed-design package i think when it will be upgraded we can remove this.

@sudhanshutech
Copy link
Member

@Aviral0702 what about those packages those needed to upgrade to support to react18. Have you not upgraded till yet? Checks are failing

@Aviral0702
Copy link
Contributor Author

Aviral0702 commented Jul 27, 2024

@Aviral0702 what about those packages those needed to upgrade to support to react18. Have you not upgraded till yet? Checks are failing

Some packages on upgrading produces graphql errors due to which Graphql Query fails to execute. I am working on it. Checks are failing because when we are trying to upgrade version of React those packages which do not support it are throwing errors leading to failure of installation of v18.

@l5io
Copy link
Contributor

l5io commented Jul 29, 2024

🚀 Preview for commit bd430fc at: https://66a76fc0dca1fe1b59d42a53--layer5.netlify.app

@l5io
Copy link
Contributor

l5io commented Aug 2, 2024

🚀 Preview for commit 9d58fc1 at: https://66ac817f0e9243e7ccef3e96--layer5.netlify.app

@l5io
Copy link
Contributor

l5io commented Aug 3, 2024

🚀 Preview for commit 8e69351 at: https://66adf5b38362b35acd52e31a--layer5.netlify.app

@l5io
Copy link
Contributor

l5io commented Aug 4, 2024

🚀 Preview for commit 6f4899f at: https://66af881a388a07a5084ab0cf--layer5.netlify.app

@l5io
Copy link
Contributor

l5io commented Aug 6, 2024

🚀 Preview for commit f099445 at: https://66b25db94ce5c52f82c973ad--layer5.netlify.app

@l5io
Copy link
Contributor

l5io commented Aug 19, 2024

🚀 Preview for commit b71e4b7 at: https://66c2b4a61f6ae6382a98d979--layer5.netlify.app

@l5io
Copy link
Contributor

l5io commented Aug 22, 2024

🚀 Preview for commit 16ebd53 at: https://66c74c11b3f6bc3a362f6fc2--layer5.netlify.app

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

4 participants