What to combine with ReactJS to assemble an analogue of AngularJS from it?

Question

JavaScript

When I found out that ReactJS is not an analogue of angularjs, I was not very upset.
But now, after reading a bunch of articles, I started building the environment and the first
thing that scared me was that the current version does not support ts. But it's okay, you can
replace babel from which I'm only scared away by the absence of class-level properties.
It's not nice when everything is in the constructor, it looks like a turkey on an oxygen cylinder.
But that is beside the point. I was advised to use redux, but the comments
disappointed me a little and I took a closer look at reflux, which is positioned
as the younger and improved brother of flux assembled by the faceboock team.
And it turned out that the client ammunition is assembled, but there is no understanding of routing.
With AngularJS, I didn't think about anything at all. And then it turned out that with routing and
all sorts of histories and other gaps.
What can you advise from the proven and how to be in general?

Answer 1

When I found out that ReactJS is not an analogue of angularjs, I was not very upset.

They shamelessly lied to you, of course there are differences, especially in terms of tracking changes, etc. but they are not so cardinal. In general, the same approach can be implemented both there and there.
blog.mgechev.com/2015/07/05/using-jsx-react-with-t...
https://github.com/Asana/typed-react/
well, roughly speaking, there were no classes in JS ...
Same as in angular - https://github.com/strml/react-router-component
No spaces. For angular, by the way, there is about the same thing, an official replacement for all sorts of uiRouters there.
This is the main problem of angular, people don't think what they are doing....
ps React, unlike angular, is a library. Flux can also be called a library. Angular (if we take the 1.x branch) is a monolithic framework. That's the whole difference. With react, you only take what you need.