Change:
Component classses created by `createClass()` return instances of `ReactComponent` when called. Most of the time when you're using React you're either creating or consuming `ReactComponent`s. <del> ### DOMElement getDOMNode() </del> <ins> #### getDOMNode ```javascript DOMElement getDOMNode() ``` </ins> If this component has been mounted into the DOM, this returns the corresponding native browser DOM element. This method is useful for reading values out of the DOM, such as form field values and performing DOM measurements. <del> ### setProps(object nextProps) </del> <ins> #### setProps ```javascript setProps(object nextProps) ``` </ins> When you're integrating with an external JavaScript application you may want to signal a change to a React component rendered with `renderComponent()`. Simply call `setProps()` to change its properties and trigger a re-render. **Note:** This method can only be called on a root-level component. That is, it's only available on the component passed directly to `renderComponent()` and none of its children. If you're inclined to use `setProps()` on a child component, instead take advantage of reactive updates and pass the new prop to the child component when it's created in `render()`. <del> ### replaceProps(object nextProps) </del> <ins> #### replaceProps ```javascript replaceProps(object nextProps) ``` </ins> Like `setProps()` but deletes any pre-existing props that are not in nextProps. <del> ### ReactComponent transferPropsTo(ReactComponent targetComponent) </del> <ins> #### transferPropsTo ```javascript ReactComponent transferPropsTo(ReactComponent targetComponent) ``` </ins> Transfer properties from this component to a target component that have not already been set on the target component. This is usually used to pass down properties to the returned root component. `targetComponent`, now updated with some new props is returned as a convenience. <del> ### setState(object nextState) </del> <ins> #### setState ```javascript setState(object nextState) ``` </ins> Merges nextState with the current state. This is the primary method you use to trigger UI updates from event handlers and server request callbacks.

Discussion:
I have a fresh installation of Ubuntu 14.04 and installed compiled version of 10.38. failed on step with error 'make: g++: Command not found'. solves the problem. It make sense put g++ dependency into Prerequisites section.
That's kind of annoying but yea, we might need to do something like that. Compilers are a dependency for any binary npm module (which one of our dependencies depends on). Even contextify itself doesn't call out the need for g**. When you install node / npm via does it not install as well? It seems like it should since that's a requirement for many modules.
I used the recommended approach for . is not a part of installation. But I see your point, contextify setup on Windows even more .
The installation of build-essential is not 'optional'. It is a prerequisite for otherwise node-gyp will fail. The instructions for the Debian-based installation should reflect that build-essential is a prerequisite.
for installing g++ in fedora and other linux os use sudo yum install /usr/bin/g++ or sudo dnf install gcc-c++
fixed it for me (Ubuntu)
works for CentOS7, too. :)
What about Mac?