React.render is deprecated

[inchr]

When I load a component with react-rails I get this warning:
Warning: React.render is deprecated. Please use ReactDOM.render from require('react-dom') instead.

Why ? I've checked and I'm running react-rails 1.5.0(that in theory is updated to react 0.14.3)

[smnplk]

Same issue here.

[SylarRuby]

Show us some code

[rmosolgo]

I'm running 1.5.0 without any warnings. I can think of a few things to try:

• Make sure to restart your development server after installing the new gem. Otherwise, it might serve an old version of the assets.
• Application code may be using React.render, you should update to ReactDOM.render.
• You may have a dependency (like a React component you downloaded) which uses React.render. You can search your dependencies and update any of them which use the old API.

If those don't help you, please paste the full stack trace here -- that will show the exact line where the React.render call is coming from. You can see the full trace by expanding the warning (Chrome):

[smnplk]

I'm using react-rails in combination with browserify-rails. I scanned the react_ujs code and I see where it is using React.render instead of ReactDom.render, so I just had to add sprockets import //= require react before //= require react_ujs and there is no more warning.

But after //= require react_ujs I am also doing //= require components where I need to require React via node module system:

var React = global.React = window.React = require('react');
var ReactDom = global.ReactDom = window.ReactDom = require('react-dom');

I hope this does not compile two same versions of react library into application.js file and makes react code load twice. Need to check that. Thanks for the tips @rmosolgo

Edit: React is loaded twice if i do this :( My setup is the same as suggested here #413 (comment).

So to sum up, if I add sprockets directive //= require react above //= require react_ujs, react will be loaded twice. If I remove //= require react, all works fine, except that render function is not called on ReactDom object, instead it's called on React. Because it looks like ReactDom is not loaded before react_ujs.js is. https://github.com/reactjs/react-rails/blob/master/lib/assets/javascripts/react_ujs.js.erb#l57

I'm using latest sprockets gem (3.5.2), browserify-rails (1.5.0) and react-rails (1.5.0)

[smnplk]

Oh, moron me. I was setting the ReactDom variable instead of ReactDOM 👊 Issue solved :)

@inchr , all you need to do is require ReactDOM.

[inchr]

Sorry guys, I was offline for holidays...
I've fixed following the @smnplk suggestions, but my code it's like this:

window.ReactDOM = require('react-dom');

(in my main.jsx, that is the entry point of webpack...I load react from webpack too, and I load the react-ujs after the bundle of webpack)

[lokeshjain2008]

@inchr If all good then close this issue.

[inchr]

@lokeshjain2008 Oh sorry, my fault! I'm new in github! done!