From 56cdf7a52d9d2d762b20405e0b285a868626a035 Mon Sep 17 00:00:00 2001 From: Abhijeet Prasad Date: Tue, 26 Sep 2023 18:22:25 -0400 Subject: [PATCH] Use correct capture name in remix docs (#7956) --- src/platforms/javascript/guides/remix/manual-setup.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/platforms/javascript/guides/remix/manual-setup.mdx b/src/platforms/javascript/guides/remix/manual-setup.mdx index 20a2c659f2fca..70cbe4c1168af 100644 --- a/src/platforms/javascript/guides/remix/manual-setup.mdx +++ b/src/platforms/javascript/guides/remix/manual-setup.mdx @@ -163,7 +163,7 @@ export const ErrorBoundary: V2_ErrorBoundaryComponent = () => { ## v2 Server-side Errors -Sentry won't be able to capture your server-side errors automatically if you're using the`v2_errorBoundary` future flag. To work around this, define a [`handleError`](https://remix.run/docs/en/main/file-conventions/entry.server#handleerror) function in your server entry point. Then use `Sentry.captureRemixServerError` to capture errors in your server-side code. +Sentry won't be able to capture your server-side errors automatically if you're using the`v2_errorBoundary` future flag. To work around this, define a [`handleError`](https://remix.run/docs/en/main/file-conventions/entry.server#handleerror) function in your server entry point. Then use `Sentry.captureRemixServerException` to capture errors in your server-side code. ```typescript {filename: entry.server.tsx} export function handleError(