React Router 4.1.1? about react-pages

[catamphetamine]

No

[catamphetamine]

An explanation for those who come here:

I would rewrite this project in react-router@4 and history@4 but

• react-router@4 is a very immature library yet, missing a lot of features react-router@3 had
• I don't trust the authors of react-router and I'm positive that they aren't competent enough so I'm gonna wait until the community fixes react-router@4 enough so that it can be used as a substitute for react-router@3
• react-router-scroll doesn't support react-router@4 for the same reasons and since this library uses react-router-scroll I'm not gonna rewrite it for react-router@4 until react-router-scroll supports it
• react-router@3 has a bug of not remounting a <Route/> when a user navigates to another URL. The authors of the library refused to fix that bug for years. I managed to find a fix for that bug and it works but I'm not sure if this fix is gonna work for react-router@4 (if you think it would then leave a comment here): there's no more custom createElement property for a <Route/>

And, there's really no need to use react-router@4 in this project since there're absolutely no features missing in react-router@3 compared to react-router@4. react-router@3 is a very stable and mature project while react-router@4 is not yet.

And also I don't like the "Everything is a React element" concept of react-router@4. E.g. why would anyone redirect not via a redirect() function but rather via first setting a state variable and then rendering a <Redirect/> element which isn't really an element and is instead some kind of a hack.

Decentralized routes in react-router@4 is yet another example of an architectural failure.

And the <Route/> name is wrong and misleading.
It should be something like <Match/> or <Location/>.

[catamphetamine]

Update: migrated the library from react-router@3 to found.
found is a better overall architecture.