Earlier quoted context omitted.
That’s because react is a library, and not a framework. React doesn’t have opinions, that’s why you can find 300 state management libraries and 200 routers which do the same thing, just in different ways.
> That’s because react is a library, and not a framework. React should be considered a framework. React absolutely imposes a data model (unidirectional workflow) to the developer thus a certain code structure. The fact that it is light weight compared to Angular doesn't change the fact that React is a front end framework. React usage completely replaces the traditional way to interact with the DOM and manage DOM even…
Quote from reactjs.org: A JavaScript library for building user interfaces
Literally on the start page