@depup/sentry__node 10.75.2-depup.0 → 11.1.0-depup.0

package/build/types-ts3.8/integrations/tracing/kafka/vendored/semconv.d.ts

@@ -1,54 +0,0 @@
-/**
- * The identifier of the partition messages are sent to or received from, unique within the `messaging.destination.name`.
- *
- * @example "1"
- *
- * @experimental This attribute is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`.
- */
-export declare const ATTR_MESSAGING_DESTINATION_PARTITION_ID: "messaging.destination.partition.id";
-/**
- * Message keys in Kafka are used for grouping alike messages to ensure they're processed on the same partition. They differ from `messaging.message.id` in that they're not unique. If the key is `null`, the attribute **MUST NOT** be set.
- *
- * @example "myKey"
- *
- * @note If the key type is not string, it's string representation has to be supplied for the attribute. If the key has no unambiguous, canonical string form, don't include its value.
- *
- * @experimental This attribute is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`.
- */
-export declare const ATTR_MESSAGING_KAFKA_MESSAGE_KEY: "messaging.kafka.message.key";
-/**
- * A boolean that is true if the message is a tombstone.
- *
- * @experimental This attribute is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`.
- */
-export declare const ATTR_MESSAGING_KAFKA_MESSAGE_TOMBSTONE: "messaging.kafka.message.tombstone";
-/**
- * The offset of a record in the corresponding Kafka partition.
- *
- * @example 42
- *
- * @experimental This attribute is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`.
- */
-export declare const ATTR_MESSAGING_KAFKA_OFFSET: "messaging.kafka.offset";
-/**
- * Enum value "process" for attribute `messaging.operation.type`.
- */
-export declare const MESSAGING_OPERATION_TYPE_VALUE_PROCESS: "process";
-/**
- * Enum value "receive" for attribute `messaging.operation.type`.
- */
-export declare const MESSAGING_OPERATION_TYPE_VALUE_RECEIVE: "receive";
-/**
- * Enum value "send" for attribute `messaging.operation.type`.
- */
-export declare const MESSAGING_OPERATION_TYPE_VALUE_SEND: "send";
-/**
- * Enum value "kafka" for attribute `messaging.system`.
- */
-export declare const MESSAGING_SYSTEM_VALUE_KAFKA: "kafka";
-/**
- * Enum value "_OTHER" for attribute `error.type`. A fallback error value to be used when
- * the instrumentation doesn't define a custom value.
- */
-export declare const ERROR_TYPE_VALUE_OTHER: "_OTHER";
-//# sourceMappingURL=semconv.d.ts.map

package/build/types-ts3.8/integrations/tracing/kafka/vendored/utils.d.ts

@@ -1,29 +0,0 @@
-import { Span, SpanAttributes, SpanLink } from '@sentry/core';
-import { KafkaMessage, Message } from './kafkajs-types';
-export interface ConsumerSpanOptions {
-    topic: string;
-    message: KafkaMessage | undefined;
-    operationType: string;
-    attributes: SpanAttributes;
-    links?: SpanLink[];
-}
-/**
- * Reads a header value off a kafkajs message as a string. kafkajs delivers headers as `Buffer`s (or
- * arrays of them), so we normalize to a string before handing them to Sentry's trace helpers.
- */
-export declare function getHeaderAsString(headers: KafkaMessage['headers'], key: string): string | undefined;
-/**
- * Builds a span link to the producer span carried in the message headers, mirroring the upstream
- * behavior of linking each batch-processed message to its originating producer span.
- */
-export declare function getLinksFromHeaders(headers: KafkaMessage['headers']): SpanLink[] | undefined;
-/** Starts an inactive consumer (process/receive) span carrying the kafkajs messaging attributes. */
-export declare function startConsumerSpan({ topic, message, operationType, links, attributes }: ConsumerSpanOptions): Span;
-/** Starts an inactive producer span and propagates its trace into the message headers. */
-export declare function startProducerSpan(topic: string, message: Message): Span;
-/**
- * Resolves once `sendPromise` settles, ending all `spans` and, on failure, marking them with the
- * error status and `error.type` before re-throwing.
- */
-export declare function endSpansOnPromise<T>(spans: Span[], sendPromise: Promise<T>): Promise<T>;
-//# sourceMappingURL=utils.d.ts.map

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

@@ -1,22 +0,0 @@
-import { KnexInstrumentation } from './vendored/instrumentation';
-export declare const instrumentKnex: ((options?: unknown) => KnexInstrumentation) & {
-    id: string;
-};
-/**
- * Knex integration
- *
- * Capture tracing data for [Knex](https://knexjs.org/).
- *
- * @example
- * ```javascript
- * import * as Sentry from '@sentry/node';
- *
- * Sentry.init({
- *  integrations: [Sentry.knexIntegration()],
- * });
- * ```
- */
-export declare const knexIntegration: () => import("@sentry/core").Integration & {
-    name: "Knex";
-};
-//# sourceMappingURL=index.d.ts.map

package/build/types-ts3.8/integrations/tracing/knex/vendored/instrumentation.d.ts

@@ -1,12 +0,0 @@
-import { InstrumentationConfig } from '@opentelemetry/instrumentation';
-import { InstrumentationBase, InstrumentationNodeModuleDefinition } from '@opentelemetry/instrumentation';
-export declare class KnexInstrumentation extends InstrumentationBase<InstrumentationConfig> {
-    constructor(config?: InstrumentationConfig);
-    init(): InstrumentationNodeModuleDefinition;
-    private _getRunnerNodeModuleFileInstrumentation;
-    private _getClientNodeModuleFileInstrumentation;
-    private _createQueryWrapper;
-    private _storeContext;
-    private _ensureWrapped;
-}
-//# sourceMappingURL=instrumentation.d.ts.map

package/build/types-ts3.8/integrations/tracing/knex/vendored/semconv.d.ts

@@ -1,7 +0,0 @@
-/**
- * @deprecated Replaced by `db.collection.name`.
- */
-export declare const ATTR_DB_SQL_TABLE: "db.sql.table";
-export declare const DB_SYSTEM_NAME_VALUE_SQLITE: "sqlite";
-export declare const DB_SYSTEM_NAME_VALUE_POSTGRESQL: "postgresql";
-//# sourceMappingURL=semconv.d.ts.map

package/build/types-ts3.8/integrations/tracing/knex/vendored/utils.d.ts

@@ -1,9 +0,0 @@
-export declare const getFormatter: (runner: any) => any;
-export declare const mapSystem: (knexSystem: string) => string;
-export declare const getName: (db: string, operation?: string, table?: string) => string;
-export declare const limitLength: (str: string, maxLength: number) => string;
-export declare const extractDatabaseFromConnectionString: (connectionString?: string) => string | undefined;
-export declare const extractHostFromConnectionString: (connectionString?: string) => string | undefined;
-export declare const extractPortFromConnectionString: (connectionString?: string) => number | undefined;
-export declare const extractTableName: (builder: any) => string;
-//# sourceMappingURL=utils.d.ts.map

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

@@ -1,72 +0,0 @@
-import { KoaInstrumentation } from './vendored/instrumentation';
-interface KoaOptions {
-    /**
-     * Ignore layers of specified types
-     */
-    ignoreLayersType?: Array<'middleware' | 'router'>;
-}
-export declare const instrumentKoa: ((options: KoaOptions | undefined) => KoaInstrumentation) & {
-    id: string;
-};
-/**
- * Adds Sentry tracing instrumentation for [Koa](https://koajs.com/).
- *
- * If you also want to capture errors, you need to call `setupKoaErrorHandler(app)` after you set up your Koa server.
- *
- * For more information, see the [koa documentation](https://docs.sentry.io/platforms/javascript/guides/koa/).
- *
- * @param {KoaOptions} options Configuration options for the Koa integration.
- *
- * @example
- * ```javascript
- * const Sentry = require('@sentry/node');
- *
- * Sentry.init({
- *   integrations: [Sentry.koaIntegration()],
- * })
- * ```
- *
- * @example
- * ```javascript
- * // To ignore middleware spans
- * const Sentry = require('@sentry/node');
- *
- * Sentry.init({
- *   integrations: [
- *     Sentry.koaIntegration({
- *       ignoreLayersType: ['middleware']
- *     })
- *   ],
- * })
- * ```
- */
-export declare const koaIntegration: (options?: KoaOptions | undefined) => import("@sentry/core").Integration & {
-    name: "Koa";
-};
-/**
- * Add an Koa error handler to capture errors to Sentry.
- *
- * The error handler must be before any other middleware and after all controllers.
- *
- * @param app The Express instances
- * @param options {ExpressHandlerOptions} Configuration options for the handler
- *
- * @example
- * ```javascript
- * const Sentry = require('@sentry/node');
- * const Koa = require("koa");
- *
- * const app = new Koa();
- *
- * Sentry.setupKoaErrorHandler(app);
- *
- * // Add your routes, etc.
- *
- * app.listen(3000);
- * ```
- */
-export declare const setupKoaErrorHandler: (app: {
-    use: (arg0: (ctx: any, next: any) => Promise<void>) => void;
-}) => void;
-export {};
-//# sourceMappingURL=index.d.ts.map

package/build/types-ts3.8/integrations/tracing/koa/vendored/enums/AttributeNames.d.ts

@@ -1,5 +0,0 @@
-export declare enum AttributeNames {
-    KOA_TYPE = "koa.type",
-    KOA_NAME = "koa.name"
-}
-//# sourceMappingURL=AttributeNames.d.ts.map

package/build/types-ts3.8/integrations/tracing/koa/vendored/instrumentation.d.ts

@@ -1,32 +0,0 @@
-import { InstrumentationBase, InstrumentationNodeModuleDefinition } from '@opentelemetry/instrumentation';
-import { KoaInstrumentationConfig } from './types';
-/** Koa instrumentation for OpenTelemetry */
-export declare class KoaInstrumentation extends InstrumentationBase<KoaInstrumentationConfig> {
-    constructor(config?: KoaInstrumentationConfig);
-    protected init(): InstrumentationNodeModuleDefinition;
-    /**
-     * Patches the Koa.use function in order to instrument each original
-     * middleware layer which is introduced
-     * @param {KoaMiddleware} middleware - the original middleware function
-     */
-    private _getKoaUsePatch;
-    /**
-     * Patches the dispatch function used by @koa/router. This function
-     * goes through each routed middleware and adds instrumentation via a call
-     * to the @function _patchLayer function.
-     * @param {KoaMiddleware} dispatchLayer - the original dispatch function which dispatches
-     * routed middleware
-     */
-    private _patchRouterDispatch;
-    /**
-     * Patches each individual @param middlewareLayer function in order to create the
-     * span and propagate context. It does not create spans when there is no parent span.
-     * @param {KoaMiddleware} middlewareLayer - the original middleware function.
-     * @param {boolean} isRouter - tracks whether the original middleware function
-     * was dispatched by the router originally
-     * @param {string?} layerPath - if present, provides additional data from the
-     * router about the routed path which the middleware is attached to
-     */
-    private _patchLayer;
-}
-//# sourceMappingURL=instrumentation.d.ts.map

package/build/types-ts3.8/integrations/tracing/koa/vendored/internal-types.d.ts

@@ -1,34 +0,0 @@
-interface DefaultState {
-}
-export type Next = () => Promise<unknown>;
-type ParameterizedContext<_StateT = DefaultState, ContextT = {}, _ResponseBodyT = unknown> = {
-    [key: string]: unknown;
-} & ContextT;
-type Middleware<StateT = DefaultState, ContextT = {}, ResponseBodyT = unknown> = (context: ParameterizedContext<StateT, ContextT, ResponseBodyT>, next: Next) => unknown;
-interface RouterParamContext<StateT = DefaultState, ContextT = {}> {
-    params: Record<string, string>;
-    router: Router<StateT, ContextT>;
-    _matchedRoute: string | RegExp | undefined;
-    _matchedRouteName: string | undefined;
-}
-interface Layer {
-    path: string | RegExp;
-    stack: KoaMiddleware[];
-}
-export interface Router<_StateT = DefaultState, _ContextT = {}> {
-    stack: Layer[];
-}
-export type KoaContext = ParameterizedContext<DefaultState, RouterParamContext>;
-export type KoaMiddleware = Middleware<DefaultState, KoaContext> & {
-    router?: Router;
-};
-/**
- * This symbol is used to mark a Koa layer as being already instrumented
- * since its possible to use a given layer multiple times (ex: middlewares)
- */
-export declare const kLayerPatched: unique symbol;
-export type KoaPatchedMiddleware = KoaMiddleware & {
-    [kLayerPatched]?: boolean;
-};
-export {};
-//# sourceMappingURL=internal-types.d.ts.map

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

@@ -1,13 +0,0 @@
-import { InstrumentationConfig } from '@opentelemetry/instrumentation';
-export declare enum KoaLayerType {
-    ROUTER = "router",
-    MIDDLEWARE = "middleware"
-}
-/**
- * Options available for the Koa Instrumentation (see [documentation](https://github.com/open-telemetry/opentelemetry-js/tree/main/packages/opentelemetry-Instrumentation-koa#koa-Instrumentation-options))
- */
-export interface KoaInstrumentationConfig extends InstrumentationConfig {
-    /** Ignore specific layers based on their type */
-    ignoreLayersType?: KoaLayerType[];
-}
-//# sourceMappingURL=types.d.ts.map

package/build/types-ts3.8/integrations/tracing/koa/vendored/utils.d.ts

@@ -1,15 +0,0 @@
-import { KoaLayerType, KoaInstrumentationConfig } from './types';
-import { KoaContext, KoaMiddleware } from './internal-types';
-import { Attributes } from '@opentelemetry/api';
-export declare const getMiddlewareMetadata: (context: KoaContext, layer: KoaMiddleware, isRouter: boolean, layerPath?: string | RegExp) => {
-    attributes: Attributes;
-    name: string;
-};
-/**
- * Check whether the given request is ignored by configuration
- * @param [list] List of ignore patterns
- * @param [onException] callback for doing something when an exception has
- *     occurred
- */
-export declare const isLayerIgnored: (type: KoaLayerType, config?: KoaInstrumentationConfig) => boolean;
-//# sourceMappingURL=utils.d.ts.map

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

@@ -1,101 +0,0 @@
-import { LangChainOptions } from '@sentry/core';
-export declare const instrumentLangChain: ((options?: LangChainOptions | undefined) => import("@opentelemetry/instrumentation").Instrumentation<import("@opentelemetry/instrumentation").InstrumentationConfig>) & {
-    id: string;
-};
-/**
- * Adds Sentry tracing instrumentation for LangChain.
- *
- * This integration is enabled by default.
- *
- * When configured, this integration automatically instruments LangChain runnable instances
- * to capture telemetry data by injecting Sentry callback handlers into all LangChain calls.
- *
- * **Important:** This integration automatically skips wrapping the OpenAI, Anthropic, and Google GenAI
- * providers to prevent duplicate spans when using LangChain with these AI providers.
- * LangChain handles the instrumentation for all underlying AI providers.
- *
- * @example
- * ```javascript
- * import * as Sentry from '@sentry/node';
- * import { ChatOpenAI } from '@langchain/openai';
- *
- * Sentry.init({
- *   integrations: [Sentry.langChainIntegration()],
- *   dataCollection: { genAI: { inputs: true, outputs: true } }, // Enable to record inputs/outputs
- * });
- *
- * // LangChain calls are automatically instrumented
- * const model = new ChatOpenAI();
- * await model.invoke("What is the capital of France?");
- * ```
- *
- * ## Manual Callback Handler
- *
- * You can also manually add the Sentry callback handler alongside other callbacks:
- *
- * @example
- * ```javascript
- * import * as Sentry from '@sentry/node';
- * import { ChatOpenAI } from '@langchain/openai';
- *
- * const sentryHandler = Sentry.createLangChainCallbackHandler({
- *   recordInputs: true,
- *   recordOutputs: true
- * });
- *
- * const model = new ChatOpenAI();
- * await model.invoke(
- *   "What is the capital of France?",
- *   { callbacks: [sentryHandler, myOtherCallback] }
- * );
- * ```
- *
- * ## Options
- *
- * - `recordInputs`: Whether to record input messages/prompts (default: follows `dataCollection.genAI.inputs`, or the deprecated `sendDefaultPii` option)
- * - `recordOutputs`: Whether to record response text (default: follows `dataCollection.genAI.outputs`, or the deprecated `sendDefaultPii` option)
- *
- * ### Default Behavior
- *
- * By default, the integration will:
- * - Record inputs and outputs based on `dataCollection.genAI` in your Sentry client options
- *   (or the deprecated `sendDefaultPii` option, for backwards compatibility)
- * - Integration-level `recordInputs`/`recordOutputs` options take precedence over global config
- *
- * @example
- * ```javascript
- * // Always record inputs and outputs regardless of global dataCollection config
- * Sentry.init({
- *   integrations: [
- *     Sentry.langChainIntegration({
- *       recordInputs: true,
- *       recordOutputs: true
- *     })
- *   ],
- * });
- *
- * // Never record inputs/outputs regardless of global dataCollection config
- * Sentry.init({
- *   dataCollection: { genAI: { inputs: true, outputs: true } },
- *   integrations: [
- *     Sentry.langChainIntegration({
- *       recordInputs: false,
- *       recordOutputs: false
- *     })
- *   ],
- * });
- * ```
- *
- * ## Supported Events
- *
- * The integration captures the following LangChain lifecycle events:
- * - LLM/Chat Model: start, end, error (via callbacks)
- * - Chain: start, end, error (via callbacks)
- * - Tool: start, end, error (via callbacks)
- * - Embeddings: embedQuery, embedDocuments (via direct method wrapping)
- *
- */
-export declare const langChainIntegration: (options?: LangChainOptions | undefined) => import("@sentry/core").Integration & {
-    name: "LangChain";
-};
-//# sourceMappingURL=index.d.ts.map

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

@@ -1,38 +0,0 @@
-import { InstrumentationBase, InstrumentationConfig, InstrumentationModuleDefinition } from '@opentelemetry/instrumentation';
-import { LangChainOptions } from '@sentry/core';
-type LangChainInstrumentationOptions = InstrumentationConfig & LangChainOptions;
-/**
- * Sentry LangChain instrumentation using OpenTelemetry.
- */
-export declare class SentryLangChainInstrumentation extends InstrumentationBase<LangChainInstrumentationOptions> {
-    constructor(config?: LangChainInstrumentationOptions);
-    /**
-     * Initializes the instrumentation by defining the modules to be patched.
-     * We patch the BaseChatModel class methods to inject callbacks
-     *
-     * We hook into provider packages (@langchain/anthropic, @langchain/openai, etc.)
-     * because @langchain/core is often bundled and not loaded as a separate module
-     */
-    init(): InstrumentationModuleDefinition | InstrumentationModuleDefinition[];
-    /**
-     * Core patch logic - patches chat model and embedding methods
-     * This is called when a LangChain provider package is loaded
-     */
-    private _patch;
-    /**
-     * Patches chat model methods (invoke, stream, batch) to inject Sentry callbacks
-     * Finds a chat model class from the provider package exports and patches its prototype methods
-     */
-    private _patchRunnableMethods;
-    /**
-     * Patches embedding class methods (embedQuery, embedDocuments) to create Sentry spans.
-     *
-     * Unlike chat models which use LangChain's callback system, the Embeddings base class
-     * has no callback support. We wrap the methods directly on the prototype.
-     *
-     * Instruments any exported class whose prototype has both embedQuery and embedDocuments as functions.
-     */
-    private _patchEmbeddingsMethods;
-}
-export {};
-//# sourceMappingURL=instrumentation.d.ts.map

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

@@ -1,77 +0,0 @@
-import { LangGraphOptions } from '@sentry/core';
-export declare const instrumentLangGraph: ((options?: LangGraphOptions | undefined) => import("@opentelemetry/instrumentation").Instrumentation<import("@opentelemetry/instrumentation").InstrumentationConfig>) & {
-    id: string;
-};
-/**
- * Adds Sentry tracing instrumentation for LangGraph.
- *
- * This integration is enabled by default.
- *
- * When configured, this integration automatically instruments LangGraph StateGraph and compiled graph instances
- * to capture telemetry data following OpenTelemetry Semantic Conventions for Generative AI.
- *
- * @example
- * ```javascript
- * import * as Sentry from '@sentry/node';
- *
- * Sentry.init({
- *   integrations: [Sentry.langGraphIntegration()],
- * });
- * ```
- *
- * ## Options
- *
- * - `recordInputs`: Whether to record prompt messages (default: follows `dataCollection.genAI.inputs`, or the deprecated `sendDefaultPii` option)
- * - `recordOutputs`: Whether to record response text (default: follows `dataCollection.genAI.outputs`, or the deprecated `sendDefaultPii` option)
- *
- * ### Default Behavior
- *
- * By default, the integration will:
- * - Record inputs and outputs based on `dataCollection.genAI` in your Sentry client options
- *   (or the deprecated `sendDefaultPii` option, for backwards compatibility)
- * - Integration-level `recordInputs`/`recordOutputs` options take precedence over global config
- *
- * @example
- * ```javascript
- * // Always record inputs and outputs regardless of global dataCollection config
- * Sentry.init({
- *   integrations: [
- *     Sentry.langGraphIntegration({
- *       recordInputs: true,
- *       recordOutputs: true
- *     })
- *   ],
- * });
- *
- * // Never record inputs/outputs regardless of global dataCollection config
- * Sentry.init({
- *   dataCollection: { genAI: { inputs: true, outputs: true } },
- *   integrations: [
- *     Sentry.langGraphIntegration({
- *       recordInputs: false,
- *       recordOutputs: false
- *     })
- *   ],
- * });
- * ```
- *
- * ## Captured Operations
- *
- * The integration captures the following LangGraph operations:
- * - **Agent Creation** (`StateGraph.compile()`) - Creates a `gen_ai.create_agent` span
- * - **Agent Invocation** (`CompiledGraph.invoke()`) - Creates a `gen_ai.invoke_agent` span
- *
- * ## Captured Data
- *
- * When `recordInputs` and `recordOutputs` are enabled, the integration captures:
- * - Input messages from the graph state
- * - Output messages and LLM responses
- * - Tool calls made during agent execution
- * - Agent and graph names
- * - Available tools configured in the graph
- *
- */
-export declare const langGraphIntegration: (options?: LangGraphOptions | undefined) => import("@sentry/core").Integration & {
-    name: "LangGraph";
-};
-//# sourceMappingURL=index.d.ts.map

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

@@ -1,19 +0,0 @@
-import { InstrumentationBase, InstrumentationConfig, InstrumentationModuleDefinition } from '@opentelemetry/instrumentation';
-import { LangGraphOptions } from '@sentry/core';
-type LangGraphInstrumentationOptions = InstrumentationConfig & LangGraphOptions;
-/**
- * Sentry LangGraph instrumentation using OpenTelemetry.
- */
-export declare class SentryLangGraphInstrumentation extends InstrumentationBase<LangGraphInstrumentationOptions> {
-    constructor(config?: LangGraphInstrumentationOptions);
-    /**
-     * Initializes the instrumentation by defining the modules to be patched.
-     */
-    init(): InstrumentationModuleDefinition[];
-    /**
-     * Core patch logic applying instrumentation to the LangGraph module.
-     */
-    private _patch;
-}
-export {};
-//# sourceMappingURL=instrumentation.d.ts.map

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

@@ -1,21 +0,0 @@
-import { LruMemoizerInstrumentation } from './vendored/instrumentation';
-export declare const instrumentLruMemoizer: ((options?: unknown) => LruMemoizerInstrumentation) & {
-    id: string;
-};
-/**
- * Adds Sentry tracing instrumentation for the [lru-memoizer](https://www.npmjs.com/package/lru-memoizer) library.
- *
- * For more information, see the [`lruMemoizerIntegration` documentation](https://docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/lrumemoizer/).
- *
- * @example
- * ```javascript
- * const Sentry = require('@sentry/node');
- *
- * Sentry.init({
- *  integrations: [Sentry.lruMemoizerIntegration()],
- * });
- */
-export declare const lruMemoizerIntegration: () => import("@sentry/core").Integration & {
-    name: "LruMemoizer";
-};
-//# sourceMappingURL=index.d.ts.map

package/build/types-ts3.8/integrations/tracing/lrumemoizer/vendored/instrumentation.d.ts

@@ -1,6 +0,0 @@
-import { InstrumentationBase, InstrumentationNodeModuleDefinition } from '@opentelemetry/instrumentation';
-export declare class LruMemoizerInstrumentation extends InstrumentationBase {
-    constructor();
-    init(): InstrumentationNodeModuleDefinition[];
-}
-//# sourceMappingURL=instrumentation.d.ts.map

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

@@ -1,22 +0,0 @@
-import { MongoDBInstrumentation } from './vendored/instrumentation';
-export declare const instrumentMongo: ((options?: unknown) => MongoDBInstrumentation) & {
-    id: string;
-};
-/**
- * Adds Sentry tracing instrumentation for the [mongodb](https://www.npmjs.com/package/mongodb) library.
- *
- * For more information, see the [`mongoIntegration` documentation](https://docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/mongo/).
- *
- * @example
- * ```javascript
- * const Sentry = require('@sentry/node');
- *
- * Sentry.init({
- *  integrations: [Sentry.mongoIntegration()],
- * });
- * ```
- */
-export declare const mongoIntegration: () => import("@sentry/core").Integration & {
-    name: "Mongo";
-};
-//# sourceMappingURL=index.d.ts.map

package/build/types-ts3.8/integrations/tracing/mongo/vendored/instrumentation.d.ts

@@ -1,11 +0,0 @@
-import { InstrumentationBase, InstrumentationNodeModuleDefinition } from '@opentelemetry/instrumentation';
-import { InstrumentationConfig } from '@opentelemetry/instrumentation';
-/** mongodb instrumentation plugin */
-export declare class MongoDBInstrumentation extends InstrumentationBase<InstrumentationConfig> {
-    constructor(config?: InstrumentationConfig);
-    init(): InstrumentationNodeModuleDefinition[];
-    private _getV3ConnectionPatches;
-    private _getV4ConnectionPoolPatches;
-    private _getV4ConnectionPatches;
-}
-//# sourceMappingURL=instrumentation.d.ts.map