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
When installing a clean instance of backstage and adding plugins, I want to encounter a clean installation without a wall of warnings in my console.
🎤 Context
There are numerous warnings that are quite worrying, e.g. React versions not matching with the versions required by core plugins or React 18 not being compatible with MUI v4. I assume the Backstage development team has ruled out that these incompatibilities are causing essential bugs. Nevertheless an output of lots of lines of warnings distract the user from actually spotting warnings that matter and should be taken seriously.
✌️ Possible Implementation
Resolve these warnings. E.g. adding react-dom and react-router-dom to the peerDependencies of a plugin created by the cli already removes several lines of warnings.
👀 Have you spent some time to check if this feature request has been raised before?
🔖 Feature description
When installing a clean instance of backstage and adding plugins, I want to encounter a clean installation without a wall of warnings in my console.
🎤 Context
There are numerous warnings that are quite worrying, e.g. React versions not matching with the versions required by core plugins or React 18 not being compatible with MUI v4. I assume the Backstage development team has ruled out that these incompatibilities are causing essential bugs. Nevertheless an output of lots of lines of warnings distract the user from actually spotting warnings that matter and should be taken seriously.
✌️ Possible Implementation
Resolve these warnings. E.g. adding react-dom and react-router-dom to the peerDependencies of a plugin created by the cli already removes several lines of warnings.
👀 Have you spent some time to check if this feature request has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else
The text was updated successfully, but these errors were encountered: