{"action":"created","issue":{"url":"https://api.github.com/repos/facebook/react/issues/6232","repository_url":"https://api.github.com/repos/facebook/react","labels_url":"https://api.github.com/repos/facebook/react/issues/6232/labels{/name}","comments_url":"https://api.github.com/repos/facebook/react/issues/6232/comments","events_url":"https://api.github.com/repos/facebook/react/issues/6232/events","html_url":"https://github.com/facebook/react/issues/6232","id":139748881,"number":6232,"title":"React DOM tree root should always have a node reference","user":{"login":"mbrio","id":13557,"avatar_url":"https://avatars.githubusercontent.com/u/13557?v=3","gravatar_id":"","url":"https://api.github.com/users/mbrio","html_url":"https://github.com/mbrio","followers_url":"https://api.github.com/users/mbrio/followers","following_url":"https://api.github.com/users/mbrio/following{/other_user}","gists_url":"https://api.github.com/users/mbrio/gists{/gist_id}","starred_url":"https://api.github.com/users/mbrio/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbrio/subscriptions","organizations_url":"https://api.github.com/users/mbrio/orgs","repos_url":"https://api.github.com/users/mbrio/repos","events_url":"https://api.github.com/users/mbrio/events{/privacy}","received_events_url":"https://api.github.com/users/mbrio/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/facebook/react/labels/Type:%20Regression","name":"Type: Regression","color":"e11d21"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":12,"created_at":"2016-03-10T00:54:47Z","updated_at":"2016-04-22T12:17:41Z","closed_at":null,"body":"I've built a task execution pipeline utilizing React v14 and I've begun testing it against React v15 and have noticed that all of a sudden I'm getting an invariant error: _React DOM tree root should always have a node reference_.\r\n\r\nWhen I comment the line that is causing this error (https://github.com/facebook/react/blob/3b96650e39ddda5ba49245713ef16dbc52d25e9e/src/renderers/dom/client/ReactDOMComponentTree.js#L171) everything works as it did with v14, and all of my unit tests pass. I assume this check is important to the new internal updates that have been made since v14.\r\n\r\nI was able to make it work with a hacky bit of code that adds properties to the instance, `_flags` and `_nativeNode`, you can see this here: https://github.com/mbrio/react-pipeline/blob/react-15/src/startTasks.js#L8-L9.\r\n\r\nI believe the issue is that with v14 I was able to use the server rendering code but in v15 I can no longer call `forceUpdate` or `setState` without errors occurring. Is there a way of bypassing the above error using the client renderer, or a way of calling `setState`/`forceUpdate` with the server renderer?"},"comment":{"url":"https://api.github.com/repos/facebook/react/issues/comments/213400749","html_url":"https://github.com/facebook/react/issues/6232#issuecomment-213400749","issue_url":"https://api.github.com/repos/facebook/react/issues/6232","id":213400749,"user":{"login":"kniknak","id":3064983,"avatar_url":"https://avatars.githubusercontent.com/u/3064983?v=3","gravatar_id":"","url":"https://api.github.com/users/kniknak","html_url":"https://github.com/kniknak","followers_url":"https://api.github.com/users/kniknak/followers","following_url":"https://api.github.com/users/kniknak/following{/other_user}","gists_url":"https://api.github.com/users/kniknak/gists{/gist_id}","starred_url":"https://api.github.com/users/kniknak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kniknak/subscriptions","organizations_url":"https://api.github.com/users/kniknak/orgs","repos_url":"https://api.github.com/users/kniknak/repos","events_url":"https://api.github.com/users/kniknak/events{/privacy}","received_events_url":"https://api.github.com/users/kniknak/received_events","type":"User","site_admin":false},"created_at":"2016-04-22T12:17:41Z","updated_at":"2016-04-22T12:17:41Z","body":"I've got same problem in Firefox. But there's no errors in Chrome. It possibly could be related with NODE_ENV = production|development and minification, I'm still trying to find out"}}