|
|
|
|
|
by kroltan
2891 days ago
|
|
I'm not sure on the "don't touch this" part, but in regards to "taking over the application", it certainly doesn't. React's entry point is the `ReactDOM.render` function, which takes some React elements, and a root node. that root node can be _any_ DOM node (Actually no idea if you can mount React into a inline SVG, but at least any _HTML_ node you certainly can). You can also have multiple `ReactDOM.render` calls, no problem at all. That initial React element can very well take values and callbacks from your Angular or whatever application. It can get messy if you nest `ReactDOM.render` within roots that are managed by React, but so would nesting any other UI framework, but the use cases for that are... Exuberantly exotic, to say the least. |
|