Merge node with javascript platform (#9710)

* Merge node with javascript platform
* Create symlinks for all previous node guides
* Fix platform icons
* Add categories to all SDKs, remove duplicate configuration where possible
* Set SDK names; change titles of Profiling pages
* Add redirects

Author: stephanie-anderson

docs/contributing/pages/components.mdx

@@ -121,7 +121,7 @@ If content is specified, it will automatically hide the content when the given `
 </Note>
 
 ```markdown {tabTitle:Example}
-<ConfigKey name="send-default-pii" notSupported={["javascript", "node"]}>
+<ConfigKey name="send-default-pii" notSupported={["javascript"]}>
 
 Description of send-default-pii
 
@@ -229,7 +229,7 @@ This will direct users to a page where they can choose the platform, and then to
 Render a section based on the currently selected `platform` in context. When the platform is not valid, the content will be hidden.
 
 ```markdown {tabTitle:Example}
-<PlatformSection notSupported={["javascript", "node"]}>
+<PlatformSection notSupported={["javascript"]}>
 
 Something that applies to all platforms, but not javascript or node.
 

docs/platforms/javascript/common/best-practices/browser-extensions.mdx

@@ -2,6 +2,14 @@
 title: Browser Extensions
 sidebar_order: 50
 description: Learn how to use Sentry in shared environments (for example in browser extensions or VSCode extensions).
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 keywords:
   [
     "BrowserClient",

docs/platforms/javascript/common/best-practices/index.mdx

@@ -2,6 +2,14 @@
 title: Best Practices
 description: "Learn how to set up Sentry in specific scenarios with those best practice guides"
 sidebar_order: 3
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 <PageGrid />

docs/platforms/javascript/common/best-practices/micro-frontends.mdx

@@ -2,6 +2,14 @@
 title: Micro Frontends
 sidebar_order: 200
 description: Learn how to identify the source of errors and route events to different Sentry projects when using micro frontend or module federation.
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 keywords:
   [
     "micro frontend",

docs/platforms/javascript/common/best-practices/multiple-sentry-instances.mdx

@@ -2,6 +2,14 @@
 title: Multiple Sentry Instances
 sidebar_order: 300
 description: Learn how to manage several Sentry instances by creating your own clients.
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 keywords:
   [
     "multiple instances",
@@ -110,5 +118,3 @@ scope1.setTag("a", "b");
 scope2.captureMessage("x");
 scope2.setTag("c", "d");
 ```
-
-

docs/platforms/javascript/common/best-practices/offline-caching.mdx

@@ -7,6 +7,13 @@ notSupported:
   - javascript.cordova
   - javascript.electron
   - javascript.wasm
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 If your JavaScript application is designed to continue working offline,

docs/platforms/javascript/common/best-practices/web-workers.mdx

@@ -15,6 +15,13 @@ notSupported:
   - javascript.react
   - javascript.vue
   - javascript.wasm
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 Sentry's Browser SDK supports [Web Workers API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API). To capture unhandled errors from Web Workers:

docs/platforms/node/common/configuration/application-not-responding.mdx renamed to docs/platforms/javascript/common/configuration/application-not-responding.mdx

@@ -2,6 +2,14 @@
 title: Application Not Responding (ANR)
 sidebar_order: 70
 description: "Learn how to turn off or specify ANRs for Node.js"
+supported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 keywords:
   [
     "anr",

docs/platforms/node/common/configuration/async-context.mdx renamed to docs/platforms/javascript/common/configuration/async-context.mdx

@@ -2,6 +2,14 @@
 title: Async Context
 sidebar_order: 80
 description: "Learn more about how to isolate Sentry scope and breadcrumbs across requests."
+supported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 You can use the `runWithAsyncContext` method to isolate Sentry scope and breadcrumbs to a single request if you are using SDK v7.48.0 or higher. This is useful if you are finding that breadcrumbs and scope are leaking across requests.

docs/platforms/javascript/common/configuration/filtering.mdx

@@ -6,8 +6,7 @@ description: "Learn more about how to configure your SDK to filter events report
 
 When you add Sentry to your app, you get a lot of valuable information about errors and performance. And lots of information is good -- as long as it's the right information, at a reasonable volume.
 
-
-Sentry offers [Inbound Filters](/product/data-management-settings/filtering/) that you can enable per project to filter out various events in sentry.io. You can use our pre-defined inbound filters (e.g. filtering known browser extensions), as well as add your own message-based filters. 
+Sentry offers [Inbound Filters](/product/data-management-settings/filtering/) that you can enable per project to filter out various events in sentry.io. You can use our pre-defined inbound filters (e.g. filtering known browser extensions), as well as add your own message-based filters.
 
 However, we recommend filtering at the client-level, because it removes the overhead of sending events you don't actually want. The Sentry SDKs have several configuration options, which are described in this document, to help you filter out events. To learn more about the event fields you can use for filtering, see [Event Payloads](https://develop.sentry.dev/sdk/event-payloads/).
 

docs/platforms/node/common/configuration/img/anr-node-example.png renamed to docs/platforms/javascript/common/configuration/img/anr-node-example.png

@@ -1,9 +1,14 @@
 ---
 title: Breadcrumbs
-excerpt: ""
 description: "Wraps native APIs to capture breadcrumbs. (default)"
-sidebar_order: 1
 notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
   - javascript.electron
 ---
 

docs/platforms/javascript/common/configuration/integrations/breadcrumbs.mdx

@@ -1,10 +1,15 @@
 ---
 title: BrowserTracing
-excerpt: ""
 description: "Capture performance data for the Browser."
-sidebar_order: 99
 notSupported:
   - javascript.cordova
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 With [performance monitoring](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services.

docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx

@@ -1,8 +1,14 @@
 ---
 title: CaptureConsole
-excerpt: ""
 description: "Captures all Console API calls via `captureException` or `captureMessage`."
-sidebar_order: 100
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 This integration captures all Console API calls and redirects them to Sentry using the SDK's captureMessage or captureException call, depending on the log level. It then re-triggers to preserve default native behavior:

docs/platforms/javascript/common/configuration/integrations/captureconsole.mdx

@@ -1,8 +1,14 @@
 ---
 title: ContextLines
-excerpt: ""
 description: "Adds source code from inline JavaScript of the current page's HTML."
-sidebar_order: 100
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 _Import name: `Sentry.contextLinesIntegration`_

docs/platforms/javascript/common/configuration/integrations/contextlines.mdx

@@ -2,6 +2,14 @@
 title: Custom Integrations
 sidebar_order: 200
 description: "Learn how you can enable a custom integration."
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 In addition to the integrations that come with the SDK, you can also write custom integrations.

docs/platforms/javascript/common/configuration/integrations/custom.mdx

@@ -1,8 +1,14 @@
 ---
 title: Debug
-excerpt: ""
 description: "Allows you to inspect the contents of a processed event and hint object that gets passed to beforeSend or beforeSendTransaction."
-sidebar_order: 100
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 This integration allows you to inspect the contents of a processed event and hint object that gets passed to `beforeSend` or `beforeSendTransaction`. It will always run as the last integration, no matter when it was registered.

docs/platforms/javascript/common/configuration/integrations/debug.mdx

@@ -1,10 +1,15 @@
 ---
 title: Dedupe
-excerpt: ""
 description: "Deduplicate certain events to avoid receiving duplicate errors. (default)"
-sidebar_order: 1
 notSupported:
   - javascript.electron
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 _Import name: `Sentry.dedupeIntegration`_

docs/platforms/javascript/common/configuration/integrations/dedupe.mdx

@@ -2,6 +2,14 @@
 title: Default Integrations
 sidebar_order: 900
 description: "Learn about default integrations, what they do, and how they hook into the standard library or the interpreter itself."
+supported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 System integrations are enabled by default to integrate into the standard library or the interpreter itself. They're documented so you can understand what they do and disable them if they cause issues.

docs/platforms/node/common/configuration/integrations/default-integrations.mdx renamed to docs/platforms/javascript/common/configuration/integrations/default-integrations.mdx

@@ -1,8 +1,14 @@
 ---
 title: ExtraErrorData
-excerpt: ""
 description: "Extracts all non-native attributes from the error object and attaches them to the event as extra data."
-sidebar_order: 100
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 This integration extracts all non-native attributes from the error object and attaches them to the event as extra data. If the error object has a .toJSON() method, the ExtraErrorData integration will run it to extract additional information.

docs/platforms/javascript/common/configuration/integrations/extraerrordata.mdx

@@ -1,8 +1,14 @@
 ---
 title: FunctionToString
-excerpt: ""
 description: "Allows the SDK to provide original functions and method names, even when those functions or methods are wrapped by our error or breadcrumb handlers. (default)"
-sidebar_order: 1
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 _Import name: `Sentry.functionToStringIntegration`_

docs/platforms/javascript/common/configuration/integrations/functiontostring.mdx

@@ -1,10 +1,15 @@
 ---
 title: GlobalHandlers
-excerpt: ""
 description: "Attaches global handlers to capture uncaught exceptions and unhandled rejections. (default)"
-sidebar_order: 1
 notSupported:
   - javascript.electron
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 _Import name: `Sentry.globalHandlersIntegration`_

docs/platforms/javascript/common/configuration/integrations/globalhandlers.mdx

@@ -1,8 +1,14 @@
 ---
 title: HttpClient
-excerpt: ""
 description: "Captures errors on failed requests from Fetch and XHR and attaches request and response information."
-sidebar_order: 100
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 This integration captures errors on failed requests from Fetch and XHR and attaches request and response information.

docs/platforms/javascript/common/configuration/integrations/httpclient.mdx

@@ -1,10 +1,15 @@
 ---
 title: HttpContext
-excerpt: ""
 description: "Attaches HTTP request information, such as URL, user-agent, referrer, and other headers to the event. (default)"
-sidebar_order: 1
 notSupported:
   - javascript.electron
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 _Import name: `Sentry.httpContextIntegration`_

docs/platforms/javascript/common/configuration/integrations/httpcontext.mdx

@@ -1,8 +1,14 @@
 ---
 title: InboundFilters
-excerpt: ""
 description: "Allows you to ignore specific errors based on the type, message, or URLs in a given exception. (default)"
-sidebar_order: 1
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 _Import name: `Sentry.inboundFiltersIntegration`_