@sentry/vite-plugin 4.3.0 → 4.5.0

package/README.md

@@ -60,6 +60,35 @@ export default defineConfig({
 });
 ```
 
+### Multi-Project Configuration
+
+If you want to upload the same source maps to multiple Sentry projects:
+
+```ts
+// vite.config.ts
+import { defineConfig } from "vite";
+import { sentryVitePlugin } from "@sentry/vite-plugin";
+
+export default defineConfig({
+  build: {
+    sourcemap: true,
+  },
+  plugins: [
+    sentryVitePlugin({
+      org: process.env.SENTRY_ORG,
+      project: ["frontend-team-a", "frontend-team-b", "frontend-team-c"],
+      authToken: process.env.SENTRY_AUTH_TOKEN,
+    }),
+  ],
+});
+```
+
+Or via environment variable:
+
+```bash
+SENTRY_PROJECT=frontend-team-a,frontend-team-b,frontend-team-c
+```
+
 ## Options
 
 -   [`org`](#org)
@@ -114,11 +143,11 @@ This value can also be specified via the `SENTRY_ORG` environment variable.
 
 ### `project`
 
+Type: `string | string[]`
 
+The slug of the Sentry project associated with the app. You can also provide an array of project slugs to upload source maps to multiple projects with the same release.
 
-The slug of the Sentry project associated with the app.
-
-This value can also be specified via the `SENTRY_PROJECT` environment variable.
+This value can also be specified via the `SENTRY_PROJECT` environment variable. To specify multiple projects via the environment variable, separate them with commas: `SENTRY_PROJECT=project1,project2,project3`.
 
 ### `authToken`
 
@@ -151,7 +180,7 @@ Additional headers to send with every outgoing request to Sentry.
 
 Type: `boolean`
 
-Enable debug information logs during build-time. Enabling this will give you, for example, logs about source maps. Defaults to `false`.
+Enable debug information logs during build-time. Enabling this will give you, for example, logs about source maps. This option also propagates the debug flag to the Sentry CLI by setting the `SENTRY_LOG_LEVEL` environment variable to `"debug"` if it's not already set. If you have explicitly set `SENTRY_LOG_LEVEL`, this option will be ignored. Defaults to `false`.
 
 ### `silent`
 
@@ -246,7 +275,7 @@ urls and absolute/relative paths). If that path doesn't exist, it then looks for
 
 Note: This is mostly helpful for complex builds with custom source map generation. For example, if you put source
 maps into a separate directory and rewrite the `//# sourceMappingURL=` comment to something other than a relative
-directory, sentry will be unable to locate the source maps for a given build artifact. This hook allows you to 
+directory, sentry will be unable to locate the source maps for a given build artifact. This hook allows you to
 implement the resolution process yourself.
 
 Use the `debug` option to print information about source map resolution.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sentry/vite-plugin",
-  "version": "4.3.0",
+  "version": "4.5.0",
   "description": "Official Sentry Vite plugin",
   "repository": "git://github.com/getsentry/sentry-javascript-bundler-plugins.git",
   "homepage": "https://github.com/getsentry/sentry-javascript-bundler-plugins/tree/main/packages/vite-plugin",
@@ -48,7 +48,7 @@
     "prepack": "ts-node ./src/prepack.ts"
   },
   "dependencies": {
-    "@sentry/bundler-plugin-core": "4.3.0",
+    "@sentry/bundler-plugin-core": "4.5.0",
     "unplugin": "1.0.1"
   },
   "devDependencies": {
@@ -57,8 +57,8 @@
     "@babel/preset-typescript": "7.17.12",
     "@rollup/plugin-babel": "5.3.1",
     "@rollup/plugin-node-resolve": "13.3.0",
-    "@sentry-internal/eslint-config": "4.3.0",
-    "@sentry-internal/sentry-bundler-plugin-tsconfig": "4.3.0",
+    "@sentry-internal/eslint-config": "4.5.0",
+    "@sentry-internal/sentry-bundler-plugin-tsconfig": "4.5.0",
     "@swc/core": "^1.2.205",
     "@swc/jest": "^0.2.21",
     "@types/jest": "^28.1.3",