Change:
**Note:** `setState()` does not immediately mutate `this.state` but creates a pending state transition. Accessing `this.state` after calling this method can potentially return the existing value. <del> ### replaceState(object nextState) </del> <ins> #### replaceState ```javascript replaceState(object nextState) ``` </ins> Like `setState()` but deletes any pre-existing state keys that are not in nextState. <del> ### forceUpdate() </del> <ins> #### forceUpdate() ```javascript forceUpdate() ``` </ins> If your `render()` method reads from something other than `this.props` or `this.state` you'll need to tell React when it needs to re-run `render()`. Use `forceUpdate()` to cause React to automatically re-render. This will cause `render()` to be called on the component and all of its children but React will only update the DOM if the markup changes. Normally you should try to avoid all uses of `forceUpdate()` and only read from `this.props` and `this.state` in `render()`. This makes your application much simpler and more efficient. <del> ### object getInitialState() ### componentWillMount() ### componentDidMount(DOMElement domNode) ### componentWillReceiveProps(object nextProps) ### boolean shouldComponentUpdate(object nextProps, object nextState) ### componentWillUpdate(object nextProps, object nextState) ### ReactComponent render() ### componentDidUpdate(object prevProps, object prevState, DOMElement domNode) ### componentWillUnmount() These are overridable lifecycle methods; see the [lifecycle methods](lifecycle.html) documentation for more information. </del> <ins> ```javascript object getInitialState() componentWillMount() componentDidMount(DOMElement domNode) componentWillReceiveProps(object nextProps) boolean shouldComponentUpdate(object nextProps, object nextState) componentWillUpdate(object nextProps, object nextState) ReactComponent render() componentDidUpdate(object prevProps, object prevState, DOMElement domNode) componentWillUnmount() ``` See the [advanced components](advanced-components.html) documentation for more details on these lifecycle methods. </ins>

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?