-
Notifications
You must be signed in to change notification settings - Fork 31
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 router migration #213
Comments
Yes, this plugin uses an old version of |
Any tips on a workaround? |
In our case, we just deactivated the plugin temporarily until this PR is merged: #190. It was blocking us to fully upgrade to the latest version of backstage, so maybe this is the best workaround for now. Or just create a fork from the code in the linked PR, which works with the latest version of react-router. |
Can we get this sort out?
|
Hi guys! |
This plugin was one that is showing [email protected]
Requesting this plugin be migrated so that it will work with the 1.6 version of Backstage with the React Router 6.0 migration
https://backstage.io/docs/tutorials/react-router-stable-migration#step-3---ensure-that-your-external-plugins-are-updated
The text was updated successfully, but these errors were encountered: