[Typo]: The mechanism described in "Providing a fallback for server errors and client-only content" behaves differently in practice

Summary

The section "Providing a fallback for server errors and client-only content" could be misleading when it comes to opting out of server-rendering.

Page

https://react.dev/reference/react/Suspense#providing-a-fallback-for-server-errors-and-client-only-content

Details

The section "Providing a fallback for server errors and client-only content" seems to suggest that if a user wants to explicitly opt out a component/hook out of being rendered on the server, they can throw an error on the server, and when that same component successfully renders on the client, the error will not be surfaced to the user. I am specifically talking about the following statements:

However, if it does not error on the client, React will not display the error to the user since the content was eventually displayed successfully.

You can use this to opt out some components from rendering on the server. To do this, throw an error in the server environment and then wrap them in a boundary to replace their HTML with fallbacks:

That seems to be in opposition to how React behaves in practice. Both in development and in production, the error thrown on the server is surfaced to the developer, and (arguably) the end user through the browser console (Minified error description: https://react.dev/errors/419).

The seems to be no documented way to distinguish an intended opt-out from a user error, and if there is none, I feel like the documentation is a bit misleading.

React Suspense のリファレンスセクション「Providing a fallback for server errors and client-only content」から始め、特にサーバーエラーとサーバーレンダリングをオプトアウトすることについての、引用されている 2 つの記述を確認してください。エラー 419 を含め、報告されている開発環境および本番環境での動作を再現または検証し、その後、セクションの説明が観測された動作と一致し、制限事項またはサポートされているアプローチを明確に示すよう更新してください。