create and use new platform include for capturing error content

Author: inventarSarah

docs/platforms/javascript/guides/nestjs/index.mdx

@@ -41,90 +41,7 @@ To import and initialize Sentry, create a file named `instrument.ts` in the root
 
 ## Step 3: Capture Nest.js Errors
 
-By default, Sentry only captures unhandled exceptions that aren't caught by an error filter.
-Additionally, `HttpException`s (including [derivatives](https://docs.nestjs.com/exception-filters#built-in-http-exceptions)) aren't captured by default because they mostly act as control flow vehicles.
-
-To make sure Sentry captures all your app's errors, configure error handling based on how your application manages exceptions:
-
-### Using a Global Catch-All Exception Filter
-
-If you have a global catch-all exception filter, add a `@SentryExceptionCaptured()` decorator to the filter's `catch()` method:
-
-```typescript {2, 6}
-import { Catch, ExceptionFilter } from "@nestjs/common";
-import { SentryExceptionCaptured } from "@sentry/nestjs";
-
-@Catch()
-export class YourCatchAllExceptionFilter implements ExceptionFilter {
-  @SentryExceptionCaptured()
-  catch(exception, host): void {
-    // your implementation here
-  }
-}
-```
-
-### Not Using a Global Catch-All Exception Filter
-
-If you don't have a global catch-all exception filter, add the `SentryGlobalFilter` to the providers of your main module, **before** any other exception filters:
-
-```typescript {2-3, 7-10}
-import { Module } from "@nestjs/common";
-import { APP_FILTER } from "@nestjs/core";
-import { SentryGlobalFilter } from "@sentry/nestjs/setup";
-
-@Module({
-  providers: [
-    {
-      provide: APP_FILTER,
-      useClass: SentryGlobalFilter,
-    },
-    // ..other providers
-  ],
-})
-export class AppModule {}
-```
-
-### Using Error Filters for Specific Exception Types
-
-If you have error filters for specific types of exceptions (for example, `@Catch(HttpException)`) and you want to report these errors to Sentry, you need to capture them in the `catch()` handler using `Sentry.captureException()`:
-
-```typescript {4,9}
-import { ArgumentsHost, BadRequestException, Catch } from "@nestjs/common";
-import { BaseExceptionFilter } from "@nestjs/core";
-import { ExampleException } from "./example.exception";
-import * as Sentry from "@sentry/nestjs";
-
-@Catch(ExampleException)
-export class ExampleExceptionFilter extends BaseExceptionFilter {
-  catch(exception: unknown, host: ArgumentsHost) {
-    Sentry.captureException(exception);
-    return super.catch(new BadRequestException(exception.message), host);
-  }
-}
-```
-
-<Expandable title="Are you using Microservices?">
-If you're using `@nestjs/microservices` make sure to handle errors in RPC contexts correctly by providing your own `RpcExceptionFilter` (see [Nest.js Microservices documentation](https://docs.nestjs.com/microservices/exception-filters)).
-`SentryGlobalFilter` in a [hybrid application](https://docs.nestjs.com/faq/hybrid-application) doesn't extend `BaseRpcExceptionFilter` since this depends on `@nestjs/microservices`.
-
-Use `Sentry.captureException(exception)` in your custom filter in case you want to send these errors to Sentry:
-
-```typescript
-import { Catch, RpcExceptionFilter, ArgumentsHost } from "@nestjs/common";
-import { Observable, throwError } from "rxjs";
-import { RpcException } from "@nestjs/microservices";
-import * as Sentry from "@sentry/nestjs";
-
-@Catch(RpcException)
-export class ExceptionFilter implements RpcExceptionFilter<RpcException> {
-  catch(exception: RpcException, host: ArgumentsHost): Observable<any> {
-    Sentry.captureException(exception); // optional
-    return throwError(() => exception.getError());
-  }
-}
-```
-
-</Expandable>
+<PlatformContent includePath="getting-started-capture-errors" />
 
 ## Step 4: Add Readable Stack Traces With Source Maps (Optional)
 

platform-includes/getting-started-capture-errors/javascript.nestjs.mdx

@@ -0,0 +1,84 @@
+By default, Sentry only captures unhandled exceptions that aren't caught by an error filter.
+Additionally, `HttpException`s (including [derivatives](https://docs.nestjs.com/exception-filters#built-in-http-exceptions)) aren't captured by default because they mostly act as control flow vehicles.
+
+To make sure Sentry captures all your app's errors, configure error handling based on how your application manages exceptions:
+
+### Using a Global Catch-All Exception Filter
+
+If you have a global catch-all exception filter, add a `@SentryExceptionCaptured()` decorator to the filter's `catch()` method:
+
+```typescript {2, 6}
+import { Catch, ExceptionFilter } from "@nestjs/common";
+import { SentryExceptionCaptured } from "@sentry/nestjs";
+
+@Catch()
+export class YourCatchAllExceptionFilter implements ExceptionFilter {
+  @SentryExceptionCaptured()
+  catch(exception, host): void {
+    // your implementation here
+  }
+}
+```
+
+### Not Using a Global Catch-All Exception Filter
+
+If you don't have a global catch-all exception filter, add the `SentryGlobalFilter` to the providers of your main module, **before** any other exception filters:
+
+```typescript {2-3, 7-10}
+import { Module } from "@nestjs/common";
+import { APP_FILTER } from "@nestjs/core";
+import { SentryGlobalFilter } from "@sentry/nestjs/setup";
+
+@Module({
+  providers: [
+    {
+      provide: APP_FILTER,
+      useClass: SentryGlobalFilter,
+    },
+    // ..other providers
+  ],
+})
+export class AppModule {}
+```
+
+### Using Error Filters for Specific Exception Types
+
+If you have error filters for specific types of exceptions (for example, `@Catch(HttpException)`) and you want to report these errors to Sentry, you need to capture them in the `catch()` handler using `Sentry.captureException()`:
+
+```typescript {4,9}
+import { ArgumentsHost, BadRequestException, Catch } from "@nestjs/common";
+import { BaseExceptionFilter } from "@nestjs/core";
+import { ExampleException } from "./example.exception";
+import * as Sentry from "@sentry/nestjs";
+
+@Catch(ExampleException)
+export class ExampleExceptionFilter extends BaseExceptionFilter {
+  catch(exception: unknown, host: ArgumentsHost) {
+    Sentry.captureException(exception);
+    return super.catch(new BadRequestException(exception.message), host);
+  }
+}
+```
+
+<Expandable title="Are you using Microservices?">
+If you're using `@nestjs/microservices` make sure to handle errors in RPC contexts correctly by providing your own `RpcExceptionFilter` (see [Nest.js Microservices documentation](https://docs.nestjs.com/microservices/exception-filters)).
+`SentryGlobalFilter` in a [hybrid application](https://docs.nestjs.com/faq/hybrid-application) doesn't extend `BaseRpcExceptionFilter` since this depends on `@nestjs/microservices`.
+
+Use `Sentry.captureException(exception)` in your custom filter in case you want to send these errors to Sentry:
+
+```typescript
+import { Catch, RpcExceptionFilter, ArgumentsHost } from "@nestjs/common";
+import { Observable, throwError } from "rxjs";
+import { RpcException } from "@nestjs/microservices";
+import * as Sentry from "@sentry/nestjs";
+
+@Catch(RpcException)
+export class ExceptionFilter implements RpcExceptionFilter<RpcException> {
+  catch(exception: RpcException, host: ArgumentsHost): Observable<any> {
+    Sentry.captureException(exception); // optional
+    return throwError(() => exception.getError());
+  }
+}
+```
+
+</Expandable>

platform-includes/getting-started-use/javascript.nestjs.mdx

@@ -34,3 +34,5 @@ import { AppService } from "./app.service";
 })
 export class AppModule {}
 ```
+
+<PlatformContent includePath="getting-started-capture-errors" />