Browse Source

Fix behavior of renderToStaticMarkup (#4600)

main
Soichiro Miki 3 years ago
committed by GitHub
parent
commit
b5c75c4290
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
  1. 2
      content/blog/2022-03-08-react-18-upgrade-guide.md

2
content/blog/2022-03-08-react-18-upgrade-guide.md

@ -296,7 +296,7 @@ If you need to support Internet Explorer we recommend you stay with React 17.
### React DOM Server {#react-dom-server}
* **`renderToString`:** Will no longer error when suspending on the server. Instead, it will emit the fallback HTML for the closest `<Suspense>` boundary and then retry rendering the same content on the client. It is still recommended that you switch to a streaming API like `renderToPipeableStream` or `renderToReadableStream` instead.
* **`renderToStaticMarkup`:** Will no longer error when suspending on the server. Instead, it will emit the fallback HTML for the closest `<Suspense>` boundary and retry rendering on the client.
* **`renderToStaticMarkup`:** Will no longer error when suspending on the server. Instead, it will emit the fallback HTML for the closest `<Suspense>` boundary.
## Changelog {#changelog}

Loading…
Cancel
Save