fix(rules): consolidate react router

[chrille0313]

Fixes #96

[chrille0313]

We could potentially consider labeling projects with react-router-dom@<7 as the old react-router-dom library and versions >= 7 as react-router, but the current rule system doesn't allow (as far as I know) to distinguishing between specific library versions

[bodinsamuel]

Thanks. I think I just messed up the names here; I should not have gone with reactrouterdom.

We can't change the ID of tech, or it will break a lot of things, so it has to stay reactrouterdom but we can change the name for sure.

Is it a problem for you? I can think of a better solution otherwise (I have none rn ahah)

[chrille0313]

We can't change the ID of tech, or it will break a lot of things, so it has to stay reactrouterdom but we can change the name for sure.

Is it a problem for you? I can think of a better solution otherwise (I have none rn ahah)

My issues are resolved as long as we can detect the npm dependency "react-router" as "React Router" and not "React Router Dom". Would this be the case if we only change the name?

[bodinsamuel]

My issues are resolved as long as we can detect the npm dependency "react-router" as "React Router" and not "React Router Dom". Would this be the case if we only change the name?

Yes should be.
I'll let you update the PR and I'll merge ☺️

[chrille0313]

Kept only the name change like requested.

[bodinsamuel]

Released under 1.27.4
Please let me know if that works for you