@sentry/rollup-plugin 2.17.0 → 2.19.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +24 -0
  2. package/package.json +4 -4
package/README.md CHANGED
@@ -85,6 +85,8 @@ export default {
85
85
  - [`uploadLegacySourcemaps`](#releaseuploadlegacysourcemaps)
86
86
  - [`reactComponentAnnotation`](#reactcomponentannotation)
87
87
  - [`enabled`](#reactcomponentannotationenabled)
88
+ - [`moduleMetadata`](#modulemetadata)
89
+ - [`applicationKey`](#applicationkey)
88
90
  - [`_experiments`](#_experiments)
89
91
  - [`injectBuildInformation`](#_experimentsinjectbuildinformation)
90
92
 
@@ -397,6 +399,8 @@ Each path can be given as a string or an object with more specific options.
397
399
  The modern version of doing source maps upload is more robust and way easier to get working but has to inject a very small snippet of JavaScript into your output bundles.
398
400
  In situations where this leads to problems (e.g subresource integrity) you can use this option as a fallback.
399
401
 
402
+ Please note that this option will not interact with any settings provided in the `sourcemaps` option. Using `uploadLegacySourcemaps` is a completely separate upload mechanism we provide for backwards-compatibility.
403
+
400
404
  The `IncludeEntry` type looks as follows:
401
405
 
402
406
  ```ts
@@ -501,6 +505,26 @@ Type: `boolean`
501
505
 
502
506
  Whether the component name annotate plugin should be enabled or not.
503
507
 
508
+ ### `moduleMetadata`
509
+
510
+ Type: `Record<string, any> | (args: { org?: string; project?: string; release?: string; }) => Record<string, any>`
511
+
512
+ Metadata that should be associated with the built application.
513
+
514
+ The metadata is serialized and can be looked up at runtime from within the SDK (for example in the `beforeSend`, event processors, or the transport), allowing for custom event filtering logic or routing of events.
515
+
516
+ Metadata can either be passed directly or alternatively a callback can be provided that will be called with the following parameters:
517
+
518
+ - `org`: The organization slug.
519
+ - `project`: The project slug.
520
+ - `release`: The release name.
521
+
522
+ ### `applicationKey`
523
+
524
+ Type: `string`
525
+
526
+ A key which will embedded in all the bundled files. The SDK will be able to use the key to apply filtering rules, for example using the `thirdPartyErrorFilterIntegration`.
527
+
504
528
  ### `_experiments`
505
529
 
506
530
  Type: `string`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sentry/rollup-plugin",
3
- "version": "2.17.0",
3
+ "version": "2.19.0",
4
4
  "description": "Official Sentry Rollup plugin",
5
5
  "repository": "git://github.com/getsentry/sentry-javascript-bundler-plugins.git",
6
6
  "homepage": "https://github.com/getsentry/sentry-javascript-bundler-plugins/tree/main/packages/rollup-plugin",
@@ -49,7 +49,7 @@
49
49
  "prepack": "ts-node ./src/prepack.ts"
50
50
  },
51
51
  "dependencies": {
52
- "@sentry/bundler-plugin-core": "2.17.0",
52
+ "@sentry/bundler-plugin-core": "2.19.0",
53
53
  "unplugin": "1.0.1"
54
54
  },
55
55
  "peerDependencies": {
@@ -61,8 +61,8 @@
61
61
  "@babel/preset-typescript": "7.17.12",
62
62
  "@rollup/plugin-babel": "5.3.1",
63
63
  "@rollup/plugin-node-resolve": "13.3.0",
64
- "@sentry-internal/eslint-config": "2.17.0",
65
- "@sentry-internal/sentry-bundler-plugin-tsconfig": "2.17.0",
64
+ "@sentry-internal/eslint-config": "2.19.0",
65
+ "@sentry-internal/sentry-bundler-plugin-tsconfig": "2.19.0",
66
66
  "@swc/core": "^1.2.205",
67
67
  "@swc/jest": "^0.2.21",
68
68
  "@types/jest": "^28.1.3",