Skip to content

Commit e2b2c9f

Browse files
mydeaclaude
andcommitted
docs(js): enable Async Context page for all server platforms
Async context isolation applies to every server-side runtime, so replace the partial pure-Node backend `supported` list with `supportedCategories: [server]`. This adds the pages for the meta-frameworks, edge runtimes (bun/deno/cloudflare), and serverless targets that were previously missing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 parent ede02ec commit e2b2c9f

1 file changed

Lines changed: 2 additions & 14 deletions

File tree

‎docs/platforms/javascript/common/configuration/async-context.mdx‎

Lines changed: 2 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -2,20 +2,8 @@
22
title: Async Context
33
sidebar_order: 80
44
description: "Learn more about how to isolate Sentry scope and breadcrumbs across requests."
5-
supported:
6-
- javascript.node
7-
- javascript.eve
8-
- javascript.mastra
9-
- javascript.aws-lambda
10-
- javascript.azure-functions
11-
- javascript.connect
12-
- javascript.express
13-
- javascript.fastify
14-
- javascript.gcp-functions
15-
- javascript.hapi
16-
- javascript.hono
17-
- javascript.koa
18-
- javascript.nestjs
5+
supportedCategories:
6+
- server
197
---
208

219
By default, the Sentry SDK will automatically isolate each request's scope and breadcrumbs. This means that any breadcrumbs or tags added will be isolated to the request. This is useful if you are finding that breadcrumbs and scope are leaking across requests. Take the following example:

0 commit comments

Comments
 (0)