react/packages/react-dom
Andrew Clark ea7b2ec289 Remove wrong return pointer warning
I'm about to refactor part of the commit phase to use recursion instead
of iteration. As part of that change, we will no longer assign the
`return` pointer when traversing into a subtree. So I'm disabling
the internal warning that fires if the return pointer is not consistent
with the parent during the commit phase.

I had originally added this warning to help prevent mistakes when
traversing the tree iteratively, but since we're intentionally switching
to recursion instead, we don't need it.
2022-04-08 17:58:52 -04:00
..
npm Move createRoot/hydrateRoot to react-dom/client (#23385) 2022-03-01 00:13:28 -05:00
src Remove wrong return pointer warning 2022-04-08 17:58:52 -04:00
README.md Fix import in README 2022-04-07 13:46:36 +01:00
client.js Fix createRoot container signature (#24110) 2022-03-16 20:06:00 -04:00
index.classic.fb.js Move unstable_scheduleHydration to ReactDOMHydrationRoot (#22455) 2021-11-15 17:15:01 -05:00
index.experimental.js Remove flushControlled from experimental releases (#23384) 2022-02-28 14:38:13 -05:00
index.js Move unstable_scheduleHydration to ReactDOMHydrationRoot (#22455) 2021-11-15 17:15:01 -05:00
index.modern.fb.js Move unstable_scheduleHydration to ReactDOMHydrationRoot (#22455) 2021-11-15 17:15:01 -05:00
index.stable.js createRoot(..., {hydrate:true}) -> hydrateRoot(...) (#21687) 2021-06-15 13:37:53 -07:00
package.json Update local package.jsons for 18 2022-03-29 12:07:33 -04:00
server.browser.js Merge /unstable-fizz entry point into /server (#21684) 2021-06-14 18:37:44 -07:00
server.js Convert the rest of react-dom and react-test-renderer to Named Exports (#18145) 2020-02-26 18:04:32 -08:00
server.node.js [Fizz/Flight] pipeToNodeWritable(..., writable).startWriting() -> renderToPipeableStream(...).pipe(writable) (#22450) 2021-10-06 00:31:06 -04:00
test-utils.js Convert the rest of react-dom and react-test-renderer to Named Exports (#18145) 2020-02-26 18:04:32 -08:00
unstable_testing.classic.fb.js Exclude react-dom/unstable_testing entry point from stable releases (#23258) 2022-02-08 23:12:31 -05:00
unstable_testing.experimental.js Exclude react-dom/unstable_testing entry point from stable releases (#23258) 2022-02-08 23:12:31 -05:00
unstable_testing.js Exclude react-dom/unstable_testing entry point from stable releases (#23258) 2022-02-08 23:12:31 -05:00
unstable_testing.modern.fb.js Exclude react-dom/unstable_testing entry point from stable releases (#23258) 2022-02-08 23:12:31 -05:00
unstable_testing.stable.js Exclude react-dom/unstable_testing entry point from stable releases (#23258) 2022-02-08 23:12:31 -05:00

README.md

react-dom

This package serves as the entry point to the DOM and server renderers for React. It is intended to be paired with the generic React package, which is shipped as react to npm.

Installation

npm install react react-dom

Usage

In the browser

import { createRoot } from 'react-dom/client';

function App() {
  return <div>Hello World</div>;
}

const root = createRoot(document.getElementById('root'));
root.render(<App />);

On the server

import { renderToPipeableStream } from 'react-dom/server';

function App() {
  return <div>Hello World</div>;
}

function handleRequest(res) {
  // ... in your server handler ...
  const stream = renderToPipeableStream(<App />, {
    onShellReady() {
      res.statusCode = 200;
      res.setHeader('Content-type', 'text/html');
      stream.pipe(res);
    },
    // ...
  });
}

API

react-dom

See https://reactjs.org/docs/react-dom.html

react-dom/client

See https://reactjs.org/docs/react-dom-client.html

react-dom/server

See https://reactjs.org/docs/react-dom-server.html