Files
react/packages/react-dom
Andrew Clark 06b7db4a10 Add experimental getDerivedStateFromCatch lifecycle
Fires during the render phase, so you can recover from an error within the same
pass. This aligns error boundaries more closely with try-catch semantics.

Let's keep this behind a feature flag until a future release. For now, the
recommendation is to keep using componentDidCatch. Eventually, the advice will
be to use getDerivedStateFromCatch for handling errors and componentDidCatch
only for logging.
2018-02-09 18:28:35 -08:00
..
2017-10-25 02:55:00 +03:00
2017-12-06 01:39:48 +00:00
2017-12-06 01:39:48 +00:00
2018-02-04 08:54:42 -08:00
2015-06-17 12:01:44 -07:00
2017-12-06 01:39:48 +00:00
2017-10-25 02:55:00 +03:00
2017-12-06 01:39:48 +00:00
2017-12-06 01:39:48 +00:00

react-dom

This package serves as the entry point of the DOM-related rendering paths. It is intended to be paired with the isomorphic React, which will be shipped as react to npm.

Installation

npm install react react-dom

Usage

In the browser

var React = require('react');
var ReactDOM = require('react-dom');

class MyComponent extends React.Component {
  render() {
    return <div>Hello World</div>;
  }
}

ReactDOM.render(<MyComponent />, node);

On the server

var React = require('react');
var ReactDOMServer = require('react-dom/server');

class MyComponent extends React.Component {
  render() {
    return <div>Hello World</div>;
  }
}

ReactDOMServer.renderToString(<MyComponent />);

API

react-dom

  • findDOMNode
  • render
  • unmountComponentAtNode

react-dom/server

  • renderToString
  • renderToStaticMarkup