You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our current project relies on the react-d3-graph library for certain functionalities. However, with the recent updates to our dependencies, particularly the update to React v18.2.0, we have encountered compatibility issues. The latest version of react-d3-graph that we use (v2.6.0) expects a peer dependency of React ^16.4.1, which is incompatible with our current React version.
Upon further investigation, it's evident that react-d3-graph is no longer actively maintained. The last release was a while ago, and there are several open issues and pull requests without recent activity.
Impact:
Build Failures: The incompatibility between our React version and the expected peer dependency of react-d3-graph is causing our front-end build step to fail.
Potential Future Issues: As react-d3-graph is not maintained, we anticipate potential bugs, security vulnerabilities, and further incompatibilities as we continue to update other parts of our project.
Stagnation: Without active maintenance, we won't benefit from any potential improvements, optimizations, or new features that a well-maintained graph library might offer.
Proposed Solution:
To ensure the stability, security, and future-proofing of our application, we propose the following steps:
Research and Identify Alternatives: Find alternative libraries or solutions that offer similar (or better) functionalities as react-d3-graph but are actively maintained and compatible with our current stack.
Refactor the Map Component: Once an alternative is chosen, refactor the Map component (and any other components relying on react-d3-graph) to use the new library or solution.
Thorough Testing: After refactoring, conduct extensive testing to ensure that the new solution integrates seamlessly and that there are no regressions.
Developer Notes
Remove the flag --legacy-peer-deps on Github Actions (github/workflows/main.yml) for front-end build stage
The text was updated successfully, but these errors were encountered:
Description:
Our current project relies on the react-d3-graph library for certain functionalities. However, with the recent updates to our dependencies, particularly the update to React v18.2.0, we have encountered compatibility issues. The latest version of react-d3-graph that we use (v2.6.0) expects a peer dependency of React ^16.4.1, which is incompatible with our current React version.
Upon further investigation, it's evident that react-d3-graph is no longer actively maintained. The last release was a while ago, and there are several open issues and pull requests without recent activity.
Impact:
Build Failures: The incompatibility between our React version and the expected peer dependency of react-d3-graph is causing our front-end build step to fail.
Potential Future Issues: As react-d3-graph is not maintained, we anticipate potential bugs, security vulnerabilities, and further incompatibilities as we continue to update other parts of our project.
Stagnation: Without active maintenance, we won't benefit from any potential improvements, optimizations, or new features that a well-maintained graph library might offer.
Proposed Solution:
To ensure the stability, security, and future-proofing of our application, we propose the following steps:
Research and Identify Alternatives: Find alternative libraries or solutions that offer similar (or better) functionalities as react-d3-graph but are actively maintained and compatible with our current stack.
Refactor the Map Component: Once an alternative is chosen, refactor the Map component (and any other components relying on react-d3-graph) to use the new library or solution.
Thorough Testing: After refactoring, conduct extensive testing to ensure that the new solution integrates seamlessly and that there are no regressions.
Developer Notes
--legacy-peer-deps
on Github Actions (github/workflows/main.yml) for front-end build stageThe text was updated successfully, but these errors were encountered: