Closed schultzp2020 closed 1 week ago
@caponetto FYI
@batzionb is this the same issue as what you documented in this Jira issue?
I just pulled the latest Backstage & orchestrator plugins and see several error modals pop up when interacting with the Orchestrator pages.
Is there a workaround for this or do I need to wait until this is resolved to use this plugin?
This issue has been closed due to the fact that the Janus community is being sunset.
For future plugin issues, please use https://github.com/backstage/community-plugins/issues
For future showcase issues, please use https://issues.redhat.com/browse/RHIDP
For more information on the sunset, see:
https://janus-idp.io/blog/2024/07/05/future-of-janus-community https://issues.redhat.com/browse/RHIDP-3690 https://issues.redhat.com/browse/RHIDP-1018
Describe the bug
Presently, the orchestrator plugin necessitates
react
andreact-dom
to be set as dev dependencies for proper resolution ofreact@18
instead ofreact@17
. This requirement arises due to the dependency on@kie-tools-core/*
and@kie-tools/*
, which currently depend onreact@17
. Consequently, eliminating the dev dependency onreact
andreact-dom
would result in the orchestrator plugin encountering conflicting versions ofreact
. Additionally, plugins should abstain from specifying versions ofreact
andreact-dom
, as this resolution should occur within the backstage instance.Solution
@kie-tools-core/*
and@kie-tools/*
to depend onreact@18
.react
andreact-dom
as dev dependencies.Expected Behavior
The plugin should work with
react
andreact-dom
set only as a peer dependency.What are the steps to reproduce this bug?
react
andreact-dom
as a dev dependencyNotice the two different versions of
react
.Versions of software used and environment
N/A