Merge branch 'master' of github.com:getsentry/sentry-docs into smi/react/router-clean-up

Author: inventarSarah

apps/changelog/package.json

@@ -25,7 +25,7 @@
     "@radix-ui/react-icons": "^1.3.2",
     "@radix-ui/react-toolbar": "^1.1.0",
     "@radix-ui/themes": "^3.1.3",
-    "@sentry/nextjs": "9.9.0",
+    "@sentry/nextjs": "9.10.1",
     "@spotlightjs/spotlight": "^2.1.1",
     "next": "15.2.3",
     "next-auth": "^4.24.5",
@@ -68,4 +68,4 @@
     "@types/react": "npm:[email protected]",
     "@types/react-dom": "npm:[email protected]"
   }
-}
+}

apps/changelog/sentry.client.config.ts renamed to apps/changelog/src/instrumentation-client.ts

@@ -1,7 +1,3 @@
-// This file configures the initialization of Sentry on the client.
-// The config you add here will be used whenever a users loads a page in their browser.
-// https://docs.sentry.io/platforms/javascript/guides/nextjs/
-
 import * as SentryCore from '@sentry/core';
 import * as Sentry from '@sentry/nextjs';
 import * as Spotlight from '@spotlightjs/spotlight';

develop-docs/development-infrastructure/continuous-integration.mdx

@@ -32,7 +32,7 @@ You might also be interested in <Link to="/development/environment/#troubleshoot
 
 **Problem:**
 
-When pushing your build to staging and you it fails the `Ensure test image` step on Travis.
+When pushing your build to staging and it fails the `Ensure test image` step on Travis.
 
 **Solution:**
 

docs/platforms/javascript/common/troubleshooting/index.mdx

@@ -159,7 +159,7 @@ A tunnel is an HTTP endpoint that acts as a proxy between Sentry and your applic
 
 Starting with version `6.7.0` of the JavaScript SDK, you can use the `tunnel` option to tell the SDK to deliver events to the configured URL, instead of using the DSN. This allows the SDK to remove `sentry_key` from the query parameters, which is one of the main reasons ad-blockers prevent sending events in the first place. This option also stops the SDK from sending preflight requests, which was one of the requirements that necessitated sending the `sentry_key` in the query parameters.
 
-To enable the `tunnel` option, provide either a relative or an absolute URL in your `Sentry.init` call. When you use a relative URL, it's relative to the current origin, and this is the form that we recommend. Using a relative URL will not trigger a preflight CORS request, so no events will be blocked, because the ad-blocker will not treat these events as third-party requests.
+To enable the `tunnel` option, provide either a relative or an absolute URL in your `Sentry.init` call. When you use a relative URL, it's relative to the current origin, and this is the form that we recommend. Using a relative URL will not trigger a preflight CORS request, so no events will be blocked, because the ad-blocker will not treat these events as third-party requests. When using tunneling with server-side SDKs like `@sentry/node` or `@sentry/bun` you must provide an absolute URL.
 
 ```javascript
 Sentry.init({

docs/platforms/javascript/guides/aws-lambda/install/cjs-layer.mdx

@@ -4,7 +4,7 @@ description: "Learn how to add the Sentry Node Lambda Layer to use Sentry in you
 sidebar_order: 1
 ---
 
-The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/Lambda/latest/dg/configuration-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](../cjs-npm).
+The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/lambda/latest/dg/adding-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](../cjs-npm).
 If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code.
 To actually start the SDK, you can decide between setting up the SDK using environment variables or in your Lambda function code. We recommend using environment variables as it's the easiest way to get started. [Initializing the SDK in code](#alternative-initialize-the-sdk-in-code) instead of setting environment variables gives you more control over the SDK setup if you need it.
 

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

@@ -44,7 +44,47 @@ Configuration should happen as early as possible in your application's lifecycle
 
 To use the SDK, initialize it in your Svelte entry point before bootstrapping your app. In a typical Svelte project, that is your `main.js` or `main.ts` file.
 
-```javascript {filename: main.js} {"onboardingOptions": {"performance": "10, 13-20", "session-replay": "11, 23-29"}}
+```javascript {tabTitle: Svelte v5+} {filename: main.js} {"onboardingOptions": {"performance": "11, 14-21", "session-replay": "12, 24-30"}}
+import { mount } from "svelte";
+import "./app.css";
+import App from "./App.svelte";
+
+import * as Sentry from "@sentry/svelte";
+
+// Initialize the Sentry SDK here
+Sentry.init({
+  dsn: "___PUBLIC_DSN___",
+  integrations: [
+    Sentry.browserTracingIntegration(),
+    Sentry.replayIntegration(),
+  ],
+
+  // Set tracesSampleRate to 1.0 to capture 100%
+  // of transactions for tracing.
+  // We recommend adjusting this value in production
+  // Learn more at
+  // https://docs.sentry.io/platforms/javascript/configuration/options/#traces-sample-rate
+  tracesSampleRate: 1.0,
+
+  // Set `tracePropagationTargets` to control for which URLs trace propagation should be enabled
+  tracePropagationTargets: ["localhost", /^https:\/\/yourserver\.io\/api/],
+
+  // Capture Replay for 10% of all sessions,
+  // plus 100% of sessions with an error
+  // Learn more at
+  // https://docs.sentry.io/platforms/javascript/session-replay/configuration/#general-integration-configuration
+  replaysSessionSampleRate: 0.1,
+  replaysOnErrorSampleRate: 1.0,
+});
+
+const app = mount(App, {
+  target: document.getElementById("app"),
+});
+
+export default app;
+```
+
+```javascript {tabTitle: Svelte v3-v4} {filename: main.js} {"onboardingOptions": {"performance": "10, 13-20", "session-replay": "11, 23-29"}}
 import "./app.css";
 import App from "./App.svelte";
 

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

@@ -18,7 +18,7 @@ Select which Sentry features you'd like to install in addition to Error Monitori
 
 <OnboardingOptionButtons options={["error-monitoring", "performance", "session-replay"]} />
 
-Sentry captures data by using an SDK within your application’s runtime.
+Sentry captures data by using an SDK within your application's runtime.
 
 ```bash {tabTitle:npm}
 npm install @sentry/vue --save
@@ -38,9 +38,7 @@ Configuration should happen as early as possible in your application's lifecycle
 
 To initialize Sentry in your Vue application, add the following code snippet to your `main.js`:
 
-### Vue 3
-
-```javascript {filename:main.js} {"onboardingOptions": {"performance": "16, 19-25", "session-replay": "17, 29-35"}}
+```javascript {tabTitle:Vue 3} {filename:main.js} {"onboardingOptions": {"performance": "16, 19-25", "session-replay": "17, 29-35"}}
 import { createApp } from "vue";
 import { createRouter } from "vue-router";
 import * as Sentry from "@sentry/vue";
@@ -82,9 +80,7 @@ app.use(router);
 app.mount("#app");
 ```
 
-### Vue 2
-
-```javascript {filename:main.js} {"onboardingOptions": {"performance": "15, 18-24", "session-replay": "16, 28-34"}}
+```javascript {tabTitle:Vue 2} {filename:main.js} {"onboardingOptions": {"performance": "15, 18-24", "session-replay": "16, 28-34"}}
 import Vue from "vue";
 import Router from "vue-router";
 import * as Sentry from "@sentry/vue";

docs/platforms/python/integrations/rust_tracing/index.mdx

@@ -3,6 +3,12 @@ title: Rust Tracing
 description: "Learn about the Rust Tracing integration and how to get performance data for Rust native extensions."
 ---
 
+<Alert>
+
+Are you using Rust (without Python) and looking for Sentry's integration with the `tracing` crate? You can find it [here](/platforms/rust/tracing/instrumentation/automatic-instrumentation/).
+
+</Alert>
+
 `RustTracingIntegration` acts as a bridge between the Sentry Python SDK and Rust's [`tracing` framework](https://tracing.rs/). With this integration, traces that begin in Python can extend into Rust seamlessly.
 
 <Alert level="warning">

docs/platforms/rust/common/tracing/index.mdx

@@ -4,6 +4,12 @@ description: "Learn how to enable tracing in your app and discover valuable perf
 sidebar_order: 4000
 ---
 
+<Alert>
+
+Are you looking for Sentry's integration with the `tracing` crate? You can find it <PlatformLink to="/tracing/instrumentation/automatic-instrumentation/">here</PlatformLink>.
+
+</Alert>
+
 With [tracing](/product/insights/), 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. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
 <Alert>

docs/product/explore/session-replay/mobile/index.mdx

@@ -6,7 +6,7 @@ description: "Use Session Replay for Mobile to get reproductions of user session
 
 Session Replay allows you to see reproductions of user sessions, which can help you understand what happened before, during, and after an error or performance issue occurred. As you play back each session, you'll be able to see every user interaction in relation to network requests, frontend and backend errors, backend spans, and more.
 
-Replays help you see exactly how the user experience is impacted by errors. Because they're integrated with our Issues product, you'll be able to see session replays connected to error events on the [Issue Details](/product/issues/issue-details/) page in Sentry. To make sure backend errors are also included in the replay, see our [backend set up instructions](/product/explore/session-replay/getting-started/#replays-for-backend-errors).
+Replays help you see exactly how the user experience is impacted by errors. Because they're integrated with our Issues product, you'll be able to see session replays connected to error events on the [Issue Details](/product/issues/issue-details/) page in Sentry. To make sure backend errors are also included in the replay, see our [backend set up instructions](/product/explore/session-replay/web/getting-started/#replays-for-backend-errors).
 
 ![Session Replay User Interface](./img/session-replay.png)