From b928920f45d92dfb953408b6adf8f97b3154433a Mon Sep 17 00:00:00 2001 From: Charly Gomez Date: Thu, 19 Sep 2024 14:29:16 +0200 Subject: [PATCH] Update docs/platforms/javascript/guides/react/features/react-router.mdx Co-authored-by: Liza Mock --- .../javascript/guides/react/features/react-router.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/platforms/javascript/guides/react/features/react-router.mdx b/docs/platforms/javascript/guides/react/features/react-router.mdx index f5d99d67fa8b1..a6ad34258d111 100644 --- a/docs/platforms/javascript/guides/react/features/react-router.mdx +++ b/docs/platforms/javascript/guides/react/features/react-router.mdx @@ -86,9 +86,9 @@ You can instrument [`createMemoryRouter`](https://reactrouter.com/en/main/router When using `react-router`, errors thrown inside route elements will only be re-thrown in **development mode**. In production, these errors won't be surfaced unless manually captured. If you **don't** have a custom error boundary in place, `react-router` will create a default one that "swallows" all errors. - -Note that this only applies to render method and lifecycle errors, since React doesn't need error boundaries to handle errors in event handlers. - + +Note, that this only applies to render method and lifecycle errors since React doesn't need error boundaries to handle errors in event handlers. + To send errors to Sentry when using a custom error boundary, use the `Sentry.captureException` method: