@depup/sentry__node 10.48.0-depup.0 → 10.67.0-depup.1

package/build/types/integrations/tracing/prisma.d.ts

@@ -1,50 +0,0 @@
-import type { Instrumentation } from '@opentelemetry/instrumentation';
-import { PrismaInstrumentation } from '@prisma/instrumentation';
-interface PrismaOptions {
-    /**
-     * @deprecated This is no longer used, v5 works out of the box.
-     */
-    prismaInstrumentation?: Instrumentation;
-    /**
-     * Configuration passed through to the {@link PrismaInstrumentation} constructor.
-     */
-    instrumentationConfig?: ConstructorParameters<typeof PrismaInstrumentation>[0];
-}
-export declare const instrumentPrisma: ((options?: PrismaOptions | undefined) => Instrumentation<import("@opentelemetry/instrumentation").InstrumentationConfig>) & {
-    id: string;
-};
-/**
- * Adds Sentry tracing instrumentation for the [prisma](https://www.npmjs.com/package/prisma) library.
- * For more information, see the [`prismaIntegration` documentation](https://docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/prisma/).
- *
- * NOTE: By default, this integration works with Prisma version 6.
- * To get performance instrumentation for other Prisma versions,
- * 1. Install the `@prisma/instrumentation` package with the desired version.
- * 1. Pass a `new PrismaInstrumentation()` instance as exported from `@prisma/instrumentation` to the `prismaInstrumentation` option of this integration:
- *
- *    ```js
- *    import { PrismaInstrumentation } from '@prisma/instrumentation'
- *
- *    Sentry.init({
- *      integrations: [
- *        prismaIntegration({
- *          // Override the default instrumentation that Sentry uses
- *          prismaInstrumentation: new PrismaInstrumentation()
- *        })
- *      ]
- *    })
- *    ```
- *
- *    The passed instrumentation instance will override the default instrumentation instance the integration would use, while the `prismaIntegration` will still ensure data compatibility for the various Prisma versions.
- * 1. Depending on your Prisma version (prior to version 6), add `previewFeatures = ["tracing"]` to the client generator block of your Prisma schema:
- *
- *    ```
- *    generator client {
- *      provider = "prisma-client-js"
- *      previewFeatures = ["tracing"]
- *    }
- *    ```
- */
-export declare const prismaIntegration: (options?: PrismaOptions | undefined) => import("@sentry/core").Integration;
-export {};
-//# sourceMappingURL=prisma.d.ts.map

package/build/types/integrations/tracing/prisma.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"prisma.d.ts","sourceRoot":"","sources":["../../../../src/integrations/tracing/prisma.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,gCAAgC,CAAC;AAEtE,OAAO,EAAE,qBAAqB,EAAE,MAAM,yBAAyB,CAAC;AAmDhE,UAAU,aAAa;IACrB;;OAEG;IACH,qBAAqB,CAAC,EAAE,eAAe,CAAC;IACxC;;OAEG;IACH,qBAAqB,CAAC,EAAE,qBAAqB,CAAC,OAAO,qBAAqB,CAAC,CAAC,CAAC,CAAC,CAAC;CAChF;AA2GD,eAAO,MAAM,gBAAgB;;CAE3B,CAAC;AAEH;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+BG;AACH,eAAO,MAAM,iBAAiB,6EAgC5B,CAAC"}

package/build/types/integrations/tracing/redis.d.ts

@@ -1,41 +0,0 @@
-import type { RedisResponseCustomAttributeFunction } from '@opentelemetry/instrumentation-ioredis';
-interface RedisOptions {
-    /**
-     * Define cache prefixes for cache keys that should be captured as a cache span.
-     *
-     * Setting this to, for example, `['user:']` will capture cache keys that start with `user:`.
-     */
-    cachePrefixes?: string[];
-    /**
-     * Maximum length of the cache key added to the span description. If the key exceeds this length, it will be truncated.
-     *
-     * Passing `0` will use the full cache key without truncation.
-     *
-     * By default, the full cache key is used.
-     */
-    maxCacheKeyLength?: number;
-}
-export declare let _redisOptions: RedisOptions;
-export declare const cacheResponseHook: RedisResponseCustomAttributeFunction;
-/** To be able to preload all Redis OTel instrumentations with just one ID ("Redis"), all the instrumentations are generated in this one function  */
-export declare const instrumentRedis: (() => void) & {
-    id: string;
-};
-/**
- * Adds Sentry tracing instrumentation for the [redis](https://www.npmjs.com/package/redis) and
- * [ioredis](https://www.npmjs.com/package/ioredis) libraries.
- *
- * For more information, see the [`redisIntegration` documentation](https://docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/redis/).
- *
- * @example
- * ```javascript
- * const Sentry = require('@sentry/node');
- *
- * Sentry.init({
- *  integrations: [Sentry.redisIntegration()],
- * });
- * ```
- */
-export declare const redisIntegration: (options?: RedisOptions | undefined) => import("@sentry/core").Integration;
-export {};
-//# sourceMappingURL=redis.d.ts.map

package/build/types/integrations/tracing/redis.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"redis.d.ts","sourceRoot":"","sources":["../../../../src/integrations/tracing/redis.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,oCAAoC,EAAE,MAAM,wCAAwC,CAAC;AAwBnG,UAAU,YAAY;IACpB;;;;OAIG;IACH,aAAa,CAAC,EAAE,MAAM,EAAE,CAAC;IACzB;;;;;;OAMG;IACH,iBAAiB,CAAC,EAAE,MAAM,CAAC;CAC5B;AAKD,eAAO,IAAI,aAAa,EAAE,YAAiB,CAAC;AAG5C,eAAO,MAAM,iBAAiB,EAAE,oCAkD/B,CAAC;AAcF,qJAAqJ;AACrJ,eAAO,MAAM,eAAe,SACtB,IAAI;;CAQT,CAAC;AAYF;;;;;;;;;;;;;;GAcG;AACH,eAAO,MAAM,gBAAgB,4EAAuC,CAAC"}

package/build/types/integrations/tracing/tedious.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"tedious.d.ts","sourceRoot":"","sources":["../../../../src/integrations/tracing/tedious.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,sBAAsB,EAAE,MAAM,wCAAwC,CAAC;AAgBhF,eAAO,MAAM,iBAAiB;;CAAiF,CAAC;AA+BhH;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,kBAAkB,0CAAyC,CAAC"}

package/build/types-ts3.8/integrations/fs.d.ts

@@ -1,24 +0,0 @@
-/**
- * This integration will create spans for `fs` API operations, like reading and writing files.
- *
- * **WARNING:** This integration may add significant overhead to your application. Especially in scenarios with a lot of
- * file I/O, like for example when running a framework dev server, including this integration can massively slow down
- * your application.
- *
- * @param options Configuration for this integration.
- */
-export declare const fsIntegration: (options?: {
-    /**
-     * Setting this option to `true` will include any filepath arguments from your `fs` API calls as span attributes.
-     *
-     * Defaults to `false`.
-     */
-    recordFilePaths?: boolean;
-    /**
-     * Setting this option to `true` will include the error messages of failed `fs` API calls as a span attribute.
-     *
-     * Defaults to `false`.
-     */
-    recordErrorMessagesAsSpanAttributes?: boolean;
-} | undefined) => import("@sentry/core").Integration;
-//# sourceMappingURL=fs.d.ts.map

package/build/types-ts3.8/integrations/tracing/prisma/vendor/v5-tracing-helper.d.ts

@@ -1,44 +0,0 @@
-import { Context, Span, SpanOptions } from '@opentelemetry/api';
-type V5SpanCallback<R> = (span?: Span, context?: Context) => R;
-type V5ExtendedSpanOptions = SpanOptions & {
-    name: string;
-    internal?: boolean;
-    middleware?: boolean;
-    active?: boolean;
-    context?: Context;
-};
-type EngineSpanEvent = {
-    span: boolean;
-    spans: V5EngineSpan[];
-};
-type V5EngineSpanKind = 'client' | 'internal';
-type V5EngineSpan = {
-    span: boolean;
-    name: string;
-    trace_id: string;
-    span_id: string;
-    parent_span_id: string;
-    start_time: [
-        number,
-        number
-    ];
-    end_time: [
-        number,
-        number
-    ];
-    attributes?: Record<string, string>;
-    links?: {
-        trace_id: string;
-        span_id: string;
-    }[];
-    kind: V5EngineSpanKind;
-};
-export interface PrismaV5TracingHelper {
-    isEnabled(): boolean;
-    getTraceParent(context?: Context): string;
-    createEngineSpan(engineSpanEvent: EngineSpanEvent): void;
-    getActiveContext(): Context | undefined;
-    runInChildSpan<R>(nameOrOptions: string | V5ExtendedSpanOptions, callback: V5SpanCallback<R>): R;
-}
-export {};
-//# sourceMappingURL=v5-tracing-helper.d.ts.map

package/build/types-ts3.8/integrations/tracing/prisma/vendor/v6-tracing-helper.d.ts

@@ -1,34 +0,0 @@
-import { Context, Span, SpanOptions } from '@opentelemetry/api';
-type V6SpanCallback<R> = (span?: Span, context?: Context) => R;
-type V6ExtendedSpanOptions = SpanOptions & {
-    name: string;
-    internal?: boolean;
-    middleware?: boolean;
-    active?: boolean;
-    context?: Context;
-};
-type V6EngineSpanId = string;
-type V6HrTime = [
-    number,
-    number
-];
-type EngineSpanKind = 'client' | 'internal';
-type PrismaV6EngineSpan = {
-    id: V6EngineSpanId;
-    parentId: string | null;
-    name: string;
-    startTime: V6HrTime;
-    endTime: V6HrTime;
-    kind: EngineSpanKind;
-    attributes?: Record<string, unknown>;
-    links?: V6EngineSpanId[];
-};
-export interface PrismaV6TracingHelper {
-    isEnabled(): boolean;
-    getTraceParent(context?: Context): string;
-    dispatchEngineSpans(spans: PrismaV6EngineSpan[]): void;
-    getActiveContext(): Context | undefined;
-    runInChildSpan<R>(nameOrOptions: string | V6ExtendedSpanOptions, callback: V6SpanCallback<R>): R;
-}
-export {};
-//# sourceMappingURL=v6-tracing-helper.d.ts.map

package/build/types-ts3.8/integrations/tracing/prisma.d.ts

@@ -1,50 +0,0 @@
-import { Instrumentation } from '@opentelemetry/instrumentation';
-import { PrismaInstrumentation } from '@prisma/instrumentation';
-interface PrismaOptions {
-    /**
-     * @deprecated This is no longer used, v5 works out of the box.
-     */
-    prismaInstrumentation?: Instrumentation;
-    /**
-     * Configuration passed through to the {@link PrismaInstrumentation} constructor.
-     */
-    instrumentationConfig?: ConstructorParameters<typeof PrismaInstrumentation>[0];
-}
-export declare const instrumentPrisma: ((options?: PrismaOptions | undefined) => Instrumentation<import("@opentelemetry/instrumentation").InstrumentationConfig>) & {
-    id: string;
-};
-/**
- * Adds Sentry tracing instrumentation for the [prisma](https://www.npmjs.com/package/prisma) library.
- * For more information, see the [`prismaIntegration` documentation](https://docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/prisma/).
- *
- * NOTE: By default, this integration works with Prisma version 6.
- * To get performance instrumentation for other Prisma versions,
- * 1. Install the `@prisma/instrumentation` package with the desired version.
- * 1. Pass a `new PrismaInstrumentation()` instance as exported from `@prisma/instrumentation` to the `prismaInstrumentation` option of this integration:
- *
- *    ```js
- *    import { PrismaInstrumentation } from '@prisma/instrumentation'
- *
- *    Sentry.init({
- *      integrations: [
- *        prismaIntegration({
- *          // Override the default instrumentation that Sentry uses
- *          prismaInstrumentation: new PrismaInstrumentation()
- *        })
- *      ]
- *    })
- *    ```
- *
- *    The passed instrumentation instance will override the default instrumentation instance the integration would use, while the `prismaIntegration` will still ensure data compatibility for the various Prisma versions.
- * 1. Depending on your Prisma version (prior to version 6), add `previewFeatures = ["tracing"]` to the client generator block of your Prisma schema:
- *
- *    ```
- *    generator client {
- *      provider = "prisma-client-js"
- *      previewFeatures = ["tracing"]
- *    }
- *    ```
- */
-export declare const prismaIntegration: (options?: PrismaOptions | undefined) => import("@sentry/core").Integration;
-export {};
-//# sourceMappingURL=prisma.d.ts.map

package/build/types-ts3.8/integrations/tracing/redis.d.ts

@@ -1,41 +0,0 @@
-import { RedisResponseCustomAttributeFunction } from '@opentelemetry/instrumentation-ioredis';
-interface RedisOptions {
-    /**
-     * Define cache prefixes for cache keys that should be captured as a cache span.
-     *
-     * Setting this to, for example, `['user:']` will capture cache keys that start with `user:`.
-     */
-    cachePrefixes?: string[];
-    /**
-     * Maximum length of the cache key added to the span description. If the key exceeds this length, it will be truncated.
-     *
-     * Passing `0` will use the full cache key without truncation.
-     *
-     * By default, the full cache key is used.
-     */
-    maxCacheKeyLength?: number;
-}
-export declare let _redisOptions: RedisOptions;
-export declare const cacheResponseHook: RedisResponseCustomAttributeFunction;
-/** To be able to preload all Redis OTel instrumentations with just one ID ("Redis"), all the instrumentations are generated in this one function  */
-export declare const instrumentRedis: (() => void) & {
-    id: string;
-};
-/**
- * Adds Sentry tracing instrumentation for the [redis](https://www.npmjs.com/package/redis) and
- * [ioredis](https://www.npmjs.com/package/ioredis) libraries.
- *
- * For more information, see the [`redisIntegration` documentation](https://docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/redis/).
- *
- * @example
- * ```javascript
- * const Sentry = require('@sentry/node');
- *
- * Sentry.init({
- *  integrations: [Sentry.redisIntegration()],
- * });
- * ```
- */
-export declare const redisIntegration: (options?: RedisOptions | undefined) => import("@sentry/core").Integration;
-export {};
-//# sourceMappingURL=redis.d.ts.map