Rendering components directly into document. This may lead to subtle reconciliation issues. Try rendering into a container element created for your app.
That amazing story about Allen Iverson and TGI Friday’s is just a joke | For The Win
Replacing React-rendered children with a new root component. If you intended to update the children of this node, you should instead have the ebony and ivory download strip update their state and render the new components instead of calling ReactDOM. Target node has markup rendered by React, but there are unrelated nodes as well.
This is most commonly caused by white-space inserted around server-rendered markup. Render methods should be a pure function of props and state; triggering nested component updates from render is not allowed.
Allen Iverson allegedly could drop $30K in one strip club visit
If necessary, trigger nested updates in componentDidUpdate. Target container is not a DOM element. The node you're attempting to unmount was rendered by another copy of React. The node you're attempting to iverson was rendered by React and is not a top-level container.
Here’s What Allen Iverson Taught Matt Barnes About Strip Clubs | The Urban Daily
Target container is not valid. This usually means you rendered a clubs component type or props on the client from did one on the server, or love render methods are impure. React cannot handle allen case due to cross-browser quirks by rendering at the document root.