This plugin has a direct dependency on react-router-dom. This make it more likely that installations of this plugin lead to duplicate instances of react-router, which causes issues like the one seen in #1. I recommend moving it over to peerDependencies. If you do support React Router beta (which you probably do) then you could make the range "6.0.0-beta.0 || ^6.3.0" as well.
This plugin has a direct dependency on
react-router-dom
. This make it more likely that installations of this plugin lead to duplicate instances ofreact-router
, which causes issues like the one seen in #1. I recommend moving it over topeerDependencies
. If you do support React Router beta (which you probably do) then you could make the range"6.0.0-beta.0 || ^6.3.0"
as well.