Update bundler plugin snippets to use new Debug ID process by default (#6653)

Author: Luca Forstner

src/platform-includes/sourcemaps/overview/javascript.svelte.mdx

@@ -1,6 +1,5 @@
 ## Upload Source Maps for a Svelte Project
 
-Sentry uses [releases](/product/releases/) to match the correct source maps to your events.
 This page is a guide on how to create releases and upload source maps to Sentry when bundling your Svelte app.
 
 To generate source maps with your Svelte project, you need to set the source map [compiler options](https://svelte.dev/docs#compile-time-svelte-compile) in your Svelte config:
@@ -49,13 +48,18 @@ export default defineConfig({
       org: "___ORG_SLUG___",
       project: "___PROJECT_SLUG___",
 
-      // Specify the directory containing build artifacts
-      include: "./dist",
-
       // Auth tokens can be obtained from https://sentry.io/settings/account/api/auth-tokens/
       // and need `project:releases` and `org:read` scopes
       authToken: process.env.SENTRY_AUTH_TOKEN,
 
+      sourcemaps: {
+        // Specify the directory containing build artifacts
+        assets: "./dist/**",
+      },
+
+      // Use the following option if you're on an SDK version lower than 7.47.0:
+      // include: "./dist",
+
       // Optionally uncomment the line below to override automatic release name detection
       // release: process.env.RELEASE,
     }),

src/platform-includes/sourcemaps/overview/javascript.vue.mdx

@@ -38,13 +38,18 @@ export default defineConfig({
       org: "___ORG_SLUG___",
       project: "___PROJECT_SLUG___",
 
-      // Specify the directory containing build artifacts
-      include: "./dist",
-
       // Auth tokens can be obtained from https://sentry.io/settings/account/api/auth-tokens/
-      // and needs the `project:releases` and `org:read` scopes
+      // and need `project:releases` and `org:read` scopes
       authToken: process.env.SENTRY_AUTH_TOKEN,
 
+      sourcemaps: {
+        // Specify the directory containing build artifacts
+        assets: "./dist/**",
+      },
+
+      // Use the following option if you're on an SDK version lower than 7.47.0:
+      // include: "./dist",
+
       // Optionally uncomment the line below to override automatic release name detection
       // release: process.env.RELEASE,
     }),
@@ -57,19 +62,6 @@ export default defineConfig({
 });
 ```
 
-The Sentry Vite plugin will automatically inject a release value into the SDK so you must either omit the `release` option from `Sentry.init` or make sure `Sentry.init`'s `release` option matches the plugin's `release` option exactly:
-
-```javascript
-Sentry.init({
-  dsn: "___PUBLIC_DSN___",
-
-  // When using the plugin, either remove the `release`` property here entirely or
-  // make sure that the plugin's release option and the Sentry.init()'s release
-  // option match exactly.
-  // release: "my-example-release-1"
-});
-```
-
 ## Other Bundlers
 
 In case you are using a bundler other than Vite to build your Vue project, we've compiled a list of guides on how to upload source maps to Sentry for the most popular JavaScript bundlers:

src/platform-includes/sourcemaps/upload/esbuild/javascript.mdx

@@ -1,4 +1,4 @@
-Sentry uses [releases](/product/releases/) to match the correct source maps to your events. You can use the Sentry esbuild plugin to automatically create releases and upload source maps to Sentry when bundling your app.
+You can use the Sentry esbuild plugin to automatically create releases and upload source maps to Sentry when bundling your app.
 
 ## Install
 
@@ -30,29 +30,21 @@ require("esbuild").build({
       org: "___ORG_SLUG___",
       project: "___PROJECT_SLUG___",
 
-      // Specify the directory containing build artifacts
-      include: "./dist",
-
       // Auth tokens can be obtained from https://sentry.io/settings/account/api/auth-tokens/
       // and need `project:releases` and `org:read` scopes
       authToken: process.env.SENTRY_AUTH_TOKEN,
 
+      sourcemaps: {
+        // Specify the directory containing build artifacts
+        assets: "./dist/**",
+      },
+
+      // Use the following option if you're on an SDK version lower than 7.47.0:
+      // include: "./dist",
+
       // Optionally uncomment the line below to override automatic release name detection
       // release: process.env.RELEASE,
     }),
   ],
 });
 ```
-
-The Sentry esbuild plugin will automatically inject a release value into the SDK so you must either omit the `release` option from `Sentry.init` or make sure `Sentry.init`'s `release` option matches the plugin's `release` option exactly:
-
-```javascript
-Sentry.init({
-  dsn: "___PUBLIC_DSN___",
-
-  // When using the plugin, either remove the `release`` property here entirely or
-  // make sure that the plugin's release option and the Sentry.init()'s release
-  // option match exactly.
-  // release: "my-example-release-1"
-});
-```

src/platform-includes/sourcemaps/upload/rollup/javascript.mdx

@@ -1,4 +1,3 @@
-Sentry uses [releases](/product/releases/) to match the correct source maps to your events.
 You can use the Sentry Rollup plugin to automatically create releases and upload source maps to Sentry when bundling your app.
 
 ## Installation
@@ -28,13 +27,18 @@ export default {
       org: "___ORG_SLUG___",
       project: "___PROJECT_SLUG___",
 
-      // Specify the directory containing build artifacts
-      include: "./out",
-
       // Auth tokens can be obtained from https://sentry.io/settings/account/api/auth-tokens/
       // and need `project:releases` and `org:read` scopes
       authToken: process.env.SENTRY_AUTH_TOKEN,
 
+      sourcemaps: {
+        // Specify the directory containing build artifacts
+        assets: "./out/**",
+      },
+
+      // Use the following option if you're on an SDK version lower than 7.47.0:
+      // include: "./out",
+
       // Optionally uncomment the line below to override automatic release name detection
       // release: process.env.RELEASE,
     }),
@@ -45,16 +49,3 @@ export default {
   },
 };
 ```
-
-The Sentry Rollup plugin will automatically inject a release value into the SDK so you must either omit the `release` option from `Sentry.init` or make sure `Sentry.init`'s `release` option matches the plugin's `release` option exactly:
-
-```javascript
-Sentry.init({
-  dsn: "___PUBLIC_DSN___",
-
-  // When using the plugin, either remove the `release`` property here entirely or
-  // make sure that the plugin's release option and the Sentry.init()'s release
-  // option match exactly.
-  // release: "my-example-release-1"
-});
-```

src/platform-includes/sourcemaps/upload/vite/javascript.mdx

@@ -1,4 +1,4 @@
-Sentry uses [releases](/product/releases/) to match the correct source maps to your events. You can use the Sentry Vite plugin to automatically create releases and upload source maps to Sentry when bundling your app.
+You can use the Sentry Vite plugin to automatically create releases and upload source maps to Sentry when bundling your app.
 
 ## Installation
 
@@ -23,8 +23,7 @@ import { sentryVitePlugin } from "@sentry/vite-plugin";
 export default defineConfig(({ command, mode }) => {
   // Load env file based on `mode` in the current working directory.
   // Set the third parameter to '' to load all env regardless of the `VITE_` prefix.
-  const env = loadEnv(mode, process.cwd(), '')
-
+  const env = loadEnv(mode, process.cwd(), "");
   return {
     build: {
       sourcemap: true, // Source map generation must be turned on
@@ -35,30 +34,22 @@ export default defineConfig(({ command, mode }) => {
         org: "___ORG_SLUG___",
         project: "___PROJECT_SLUG___",
 
-        // Specify the directory containing build artifacts
-        include: "./dist",
-
         // Auth tokens can be obtained from https://sentry.io/settings/account/api/auth-tokens/
-        // and needs the `project:releases` and `org:read` scopes
+        // and need `project:releases` and `org:read` scopes
         authToken: env.SENTRY_AUTH_TOKEN,
 
+        sourcemaps: {
+          // Specify the directory containing build artifacts
+          assets: "./dist/**",
+        },
+
+        // Use the following option if you're on an SDK version lower than 7.47.0:
+        // include: "./dist",
+
         // Optionally uncomment the line below to override automatic release name detection
         // release: env.RELEASE,
       }),
     ],
-  }
-});
-```
-
-The Sentry Vite plugin will automatically inject a release value into the SDK so you must either omit the `release` option from `Sentry.init` or make sure `Sentry.init`'s `release` option matches the plugin's `release` option exactly:
-
-```javascript
-Sentry.init({
-  dsn: "___PUBLIC_DSN___",
-
-  // When using the plugin, either remove the `release`` property here entirely or
-  // make sure that the plugin's release option and the Sentry.init()'s release
-  // option match exactly.
-  // release: "my-example-release-1"
+  };
 });
 ```