From d615fe40a1913b0572a47aaf8c006b466976f7fc Mon Sep 17 00:00:00 2001 From: Dan Abramov Date: Thu, 27 Jul 2017 23:44:43 +0100 Subject: [PATCH] Make it more specific --- _posts/2017-07-26-error-handling-in-react-16.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2017-07-26-error-handling-in-react-16.md b/_posts/2017-07-26-error-handling-in-react-16.md index 574716ad..3dd7ecdf 100644 --- a/_posts/2017-07-26-error-handling-in-react-16.md +++ b/_posts/2017-07-26-error-handling-in-react-16.md @@ -77,7 +77,7 @@ We also encourage you to use JS error reporting services (or build your own) so ## Component Stack Traces -React 16 prints all errors to the console in development, even if the application accidentally swallows them. In addition to the error message and the JavaScript stack, it also provides component stack traces. Now you can see where exactly in the component tree the failure has happened: +React 16 prints all errors that occurred during rendering to the console in development, even if the application accidentally swallows them. In addition to the error message and the JavaScript stack, it also provides component stack traces. Now you can see where exactly in the component tree the failure has happened: Component stack traces in error message