From b5c75c4290d8394c34c980baed0935eeec97883e Mon Sep 17 00:00:00 2001 From: Soichiro Miki Date: Tue, 26 Apr 2022 10:19:49 +0900 Subject: [PATCH] Fix behavior of renderToStaticMarkup (#4600) --- content/blog/2022-03-08-react-18-upgrade-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2022-03-08-react-18-upgrade-guide.md b/content/blog/2022-03-08-react-18-upgrade-guide.md index e1195189..c685aaa6 100644 --- a/content/blog/2022-03-08-react-18-upgrade-guide.md +++ b/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 `` 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 `` 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 `` boundary. ## Changelog {#changelog}