replaceState void replaceState( object nextState, [function callback] )

React lets you use whatever style of data management you want, including mutation. However, if you can use immutable data in performance-critical parts of your application

After building your component, you may find yourself wanting to "reach out" and invoke methods on component instances returned from render(). In most cases, this

Updating: componentDidUpdate void componentDidUpdate( object prevProps, object prevState

React.cloneElement ReactElement cloneElement( ReactElement element, [object props]

One of React's biggest strengths is that it's easy to track the flow of data through your React components. When you look at a component, you can easily see exactly which props

JSX looks like HTML but there are some important differences you may run into. For DOM differences, such as the inline style

Form components such as <input>, <textarea>, and <option> differ from other native components because they can be mutated

For parent-child communication, simply pass props. For child-parent

if-else statements don't work inside JSX. This is because JSX is just syntactic sugar for function calls and object construction. Take this basic example: