@sentry/bundler-plugin-core - npm Package Compare versions

Comparing version 2.17.0 to 2.18.0

dist/types/index.d.ts

@@ -7,3 +7,3 @@ import { TransformResult, UnpluginOptions } from "unplugin";
     componentNameAnnotatePlugin?: () => UnpluginOptions;
-    moduleMetadataInjectionPlugin?: (injectionCode: string) => UnpluginOptions;
+    moduleMetadataInjectionPlugin: (injectionCode: string) => UnpluginOptions;
     debugIdInjectionPlugin: (logger: Logger) => UnpluginOptions;
@@ -10,0 +10,0 @@ debugIdUploadPlugin: (upload: (buildArtifacts: string[]) => Promise<void>) => UnpluginOptions;

dist/types/options-mapping.d.ts

@@ -65,5 +65,12 @@ import { Logger } from "./sentry/logger";
     } | undefined;
+    _metaOptions: {
+        telemetry: {
+            metaFramework: string | undefined;
+        };
+    };
+    applicationKey: string | undefined;
+    moduleMetadata: import("./types").ModuleMetadata | undefined;
     _experiments: {
         injectBuildInformation?: boolean | undefined;
-        moduleMetadata?: any;
+        moduleMetadata?: import("./types").ModuleMetadata | import("./types").ModuleMetadataCallback | undefined;
     };
@@ -70,0 +77,0 @@ };

dist/types/types.d.ts

@@ -267,2 +267,20 @@ export interface Options {
     /**
+     * Metadata that should be associated with the built application.
+     *
+     * 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.
+     *
+     * Metadata can either be passed directly or alternatively a callback can be provided that will be
+     * called with the following parameters:
+     * - `org`: The organization slug.
+     * - `project`: The project slug.
+     * - `release`: The release name.
+     */
+    moduleMetadata?: ModuleMetadata | ModuleMetadataCallback;
+    /**
+     * 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`.
+     */
+    applicationKey?: string;
+    /**
      * Options that are considered experimental and subject to change.
@@ -281,13 +299,18 @@ *
         /**
-         * Metadata associated with this module.
+         * NOTE: This option has been promoted to stable.
          *
-         * The metadata is serialized and can be looked up at runtime by filename.
+         * Metadata that should be associated with the built application.
          *
+         * 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.
+         *
          * Metadata can either be passed directly or alternatively a callback can be provided that will be
-         * called with the following arguments:
+         * called with the following parameters:
          * - `org`: The organization slug.
          * - `project`: The project slug.
          * - `release`: The release name.
+         *
+         * @deprecated Use the non-experimental `moduleMetadata` option instead. (Basically just move this option out of `_experiments`)
          */
-        moduleMetadata?: any | ModuleMetadataCallback;
+        moduleMetadata?: ModuleMetadata | ModuleMetadataCallback;
     };
@@ -305,4 +328,16 @@ /**
         loggerPrefixOverride?: string;
+        /**
+         * Arbitrary telemetry items.
+         */
+        telemetry?: {
+            /**
+             * The meta framework using the plugin.
+             */
+            metaFramework?: string;
+        };
     };
 }
+export interface ModuleMetadata {
+    [key: string]: any;
+}
 export interface ModuleMetadataCallbackArgs {
@@ -313,3 +348,3 @@ org?: string;
 }
-export type ModuleMetadataCallback = (args: ModuleMetadataCallbackArgs) => object;
+export type ModuleMetadataCallback = (args: ModuleMetadataCallbackArgs) => ModuleMetadata;
 export type IncludeEntry = {
@@ -316,0 +351,0 @@ /**

package.json

 {
   "name": "@sentry/bundler-plugin-core",
-  "version": "2.17.0",
+  "version": "2.18.0",
   "description": "Sentry Bundler Plugin Core",
@@ -56,3 +56,3 @@ "repository": "git://github.com/getsentry/sentry-javascript-bundler-plugins.git",
     "@babel/core": "^7.18.5",
-    "@sentry/babel-plugin-component-annotate": "2.17.0",
+    "@sentry/babel-plugin-component-annotate": "2.18.0",
     "@sentry/cli": "^2.22.3",
@@ -72,4 +72,4 @@ "dotenv": "^16.3.1",
     "@rollup/plugin-replace": "^4.0.0",
-    "@sentry-internal/eslint-config": "2.17.0",
-    "@sentry-internal/sentry-bundler-plugin-tsconfig": "2.17.0",
+    "@sentry-internal/eslint-config": "2.18.0",
+    "@sentry-internal/sentry-bundler-plugin-tsconfig": "2.18.0",
     "@sentry/node": "7.102.0",
@@ -76,0 +76,0 @@ "@sentry/utils": "7.102.0",

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

2890766

increased by0.4%

Lines of code

27365

increased by0.31%

Dependency changes

• + Added@sentry/babel-plugin-component-annotate@2.18.0(transitive)

• - Removed@sentry/babel-plugin-component-annotate@2.17.0(transitive)

• Updated@sentry/babel-plugin-component-annotate@2.18.0