fix: Move react strict dependencies #49
Merged
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
packages.json defines react dependencies as strict dependencies instead of peerDependencies and devDependencies. This prevents the plugin to use the version of React define by the installation and instead forced the one used in the project.
This causes the plugin installation to fail in configurations where the React version doesn't match the one defined in the plugin.
This PR moves React dependencies into peerDependencies to allow the plugin to use the version defined in the Backstage configuration and devDependencies to allow tests to run successfully.
It also upgrades Backstage packages to the latest version.
Type of change
Checklist
If this is a breaking change 👇
Acknowledgement
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.