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

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

@@ -1,54 +0,0 @@
-export interface FieldDef {
-    name: string;
-    tableID: number;
-    columnID: number;
-    dataTypeID: number;
-    dataTypeSize: number;
-    dataTypeModifier: number;
-    format: string;
-}
-export interface QueryResultBase {
-    command: string;
-    rowCount: number | null;
-    oid: number;
-    fields: FieldDef[];
-}
-export interface QueryResult<R = any> extends QueryResultBase {
-    rows: R[];
-}
-export interface QueryArrayResult<R extends any[] = any[]> extends QueryResultBase {
-    rows: R[];
-}
-export interface PgClientBase {
-    connect(): Promise<void>;
-    connect(callback: (err: Error) => void): void;
-    query(...args: any[]): any;
-    copyFrom(queryText: string): any;
-    copyTo(queryText: string): any;
-    pauseDrain(): void;
-    resumeDrain(): void;
-    escapeIdentifier(str: string): string;
-    escapeLiteral(str: string): string;
-    on(event: 'drain', listener: () => void): this;
-    on(event: 'error', listener: (err: Error) => void): this;
-    on(event: 'notice', listener: (notice: any) => void): this;
-    on(event: 'notification', listener: (message: any) => void): this;
-    on(event: 'end', listener: () => void): this;
-    on(event: string, listener: (...args: any[]) => void): this;
-    [key: string]: any;
-}
-export interface PgClient extends PgClientBase {
-    user?: string | undefined;
-    database?: string | undefined;
-    port: number;
-    host: string;
-    password?: string | undefined;
-    ssl: boolean;
-    readonly connection: any;
-    end(): Promise<void>;
-    end(callback: (err: Error) => void): void;
-}
-export interface PgPoolClient extends PgClientBase {
-    release(err?: Error | boolean): void;
-}
-//# sourceMappingURL=pg-types.d.ts.map

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

@@ -1,13 +0,0 @@
-/**
- * Deprecated, use `server.address`, `server.port` attributes instead.
- *
- * @example "Server=(localdb)\\v11.0;Integrated Security=true;"
- *
- * @deprecated Replaced by `server.address` and `server.port`.
- */
-export declare const ATTR_DB_CONNECTION_STRING: "db.connection_string";
-/**
- * Enum value "postgresql" for attribute `db.system`.
- */
-export declare const DB_SYSTEM_VALUE_POSTGRESQL: "postgresql";
-//# sourceMappingURL=semconv.d.ts.map

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

@@ -1,11 +0,0 @@
-import { InstrumentationConfig } from '@opentelemetry/instrumentation';
-export interface PgInstrumentationConfig extends InstrumentationConfig {
-    /**
-     * If true, `pg.connect` and `pg-pool.connect` spans will not be created.
-     * Query spans are still recorded.
-     *
-     * @default false
-     */
-    ignoreConnectSpans?: boolean;
-}
-//# sourceMappingURL=types.d.ts.map

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

@@ -1,56 +0,0 @@
-import { Span, SpanAttributes } from '@sentry/core';
-import { PgClientExtended, PgParsedConnectionParams, PgPoolCallback, PgPoolOptionsParams, PostgresCallback } from './internal-types';
-export declare const ORIGIN = "auto.db.otel.postgres";
-/**
- * Helper function to get a low cardinality span name from whatever info we have
- * about the query.
- *
- * This is tricky, because we don't have most of the information (table name,
- * operation name, etc) the spec recommends using to build a low-cardinality
- * value w/o parsing. So, we use db.name and assume that, if the query's a named
- * prepared statement, those `name` values will be low cardinality. If we don't
- * have a named prepared statement, we try to parse an operation (despite the
- * spec's warnings).
- *
- * @params dbName The name of the db against which this query is being issued,
- *   which could be missing if no db name was given at the time that the
- *   connection was established.
- * @params queryConfig Information we have about the query being issued, typed
- *   to reflect only the validation we've actually done on the args to
- *   `client.query()`. This will be undefined if `client.query()` was called
- *   with invalid arguments.
- */
-export declare function getQuerySpanName(dbName: string | undefined, queryConfig?: {
-    text: string;
-    name?: unknown;
-}): string;
-export declare function parseNormalizedOperationName(queryText: string): string;
-export declare function parseAndMaskConnectionString(connectionString: string): string;
-export declare function getConnectionString(params: PgParsedConnectionParams | PgPoolOptionsParams): string;
-export declare function getSemanticAttributesFromConnection(params: PgParsedConnectionParams): SpanAttributes;
-export declare function getSemanticAttributesFromPoolConnection(params: PgPoolOptionsParams): SpanAttributes;
-/**
- * The SDK always requires a parent span (it sets `requireParentSpan: true`), so
- * we only instrument when there is an active span to parent the new span under.
- */
-export declare function shouldSkipInstrumentation(): boolean;
-export declare function handleConfigQuery(this: PgClientExtended, queryConfig?: {
-    text: string;
-    values?: unknown;
-    name?: unknown;
-}): Span;
-export declare function patchCallback(span: Span, cb: PostgresCallback): PostgresCallback;
-export declare function patchCallbackPGPool(span: Span, cb: PgPoolCallback): PgPoolCallback;
-export declare function patchClientConnectCallback(span: Span, cb: (...args: unknown[]) => void): (...args: unknown[]) => void;
-/**
- * Attempt to get a message string from a thrown value, while being quite
- * defensive, to recognize the fact that, in JS, any kind of value (even
- * primitives) can be thrown.
- */
-export declare function getErrorMessage(e: unknown): string | undefined;
-export declare function isObjectWithTextString(it: unknown): it is ObjectWithText;
-export type ObjectWithText = {
-    text: string;
-    [k: string]: unknown;
-};
-//# sourceMappingURL=utils.d.ts.map

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

@@ -1,103 +0,0 @@
-import { InstrumentationConfig } from '@opentelemetry/instrumentation';
-import { InstrumentationBase, InstrumentationNodeModuleDefinition } from '@opentelemetry/instrumentation';
-import { Span } from '@sentry/core';
-type PostgresConnectionContext = {
-    ATTR_DB_NAMESPACE?: string;
-    ATTR_SERVER_ADDRESS?: string;
-    ATTR_SERVER_PORT?: string;
-};
-type PostgresJsInstrumentationConfig = InstrumentationConfig & {
-    /**
-     * Whether to require a parent span for the instrumentation.
-     * If set to true, the instrumentation will only create spans if there is a parent span
-     * available in the current scope.
-     * @default true
-     */
-    requireParentSpan?: boolean;
-    /**
-     * Hook to modify the span before it is started.
-     * This can be used to set additional attributes or modify the span in any way.
-     */
-    requestHook?: (span: Span, sanitizedSqlQuery: string, postgresConnectionContext?: PostgresConnectionContext) => void;
-};
-export declare const instrumentPostgresJs: ((options?: PostgresJsInstrumentationConfig | undefined) => PostgresJsInstrumentation) & {
-    id: string;
-};
-/**
- * Instrumentation for the [postgres](https://www.npmjs.com/package/postgres) library.
- * This instrumentation captures postgresjs queries and their attributes.
- *
- * Uses internal Sentry patching patterns to support both CommonJS and ESM environments.
- */
-export declare class PostgresJsInstrumentation extends InstrumentationBase<PostgresJsInstrumentationConfig> {
-    constructor(config: PostgresJsInstrumentationConfig);
-    /**
-     * Initializes the instrumentation by patching the postgres module.
-     * Uses two complementary approaches:
-     * 1. Main function wrapper: instruments sql instances created AFTER instrumentation is set up (CJS + ESM)
-     * 2. Query.prototype patch: fallback for sql instances created BEFORE instrumentation (CJS only)
-     */
-    init(): InstrumentationNodeModuleDefinition;
-    /**
-     * Patches the postgres module by wrapping the main export function.
-     * This intercepts the creation of sql instances and instruments them.
-     */
-    private _patchPostgres;
-    /**
-     * Determines whether a span should be created based on the current context.
-     * If `requireParentSpan` is set to true in the configuration, a span will
-     * only be created if there is a parent span available.
-     */
-    private _shouldCreateSpans;
-    /**
-     * Extracts DB operation name from SQL query and sets it on the span.
-     */
-    private _setOperationName;
-    /**
-     * Reconstructs the full SQL query from template strings with PostgreSQL placeholders.
-     *
-     * For sql`SELECT * FROM users WHERE id = ${123} AND name = ${'foo'}`:
-     *   strings = ["SELECT * FROM users WHERE id = ", " AND name = ", ""]
-     *   returns: "SELECT * FROM users WHERE id = $1 AND name = $2"
-     */
-    private _reconstructQuery;
-    /**
-     * Sanitize SQL query as per the OTEL semantic conventions
-     * https://opentelemetry.io/docs/specs/semconv/database/database-spans/#sanitization-of-dbquerytext
-     *
-     * PostgreSQL $n placeholders are preserved per OTEL spec - they're parameterized queries,
-     * not sensitive literals. Only actual values (strings, numbers, booleans) are sanitized.
-     */
-    private _sanitizeSqlQuery;
-    /**
-     * Fallback patch for Query.prototype.handle to instrument queries from pre-existing sql instances.
-     * This catches queries from sql instances created BEFORE Sentry was initialized (CJS only).
-     *
-     * Note: Queries from pre-existing instances won't have connection context (database, host, port)
-     * because the sql instance wasn't created through our instrumented wrapper.
-     */
-    private _patchQueryPrototype;
-    /**
-     * Restores the original Query.prototype.handle method.
-     */
-    private _unpatchQueryPrototype;
-}
-/**
- * Adds Sentry tracing instrumentation for the [postgres](https://www.npmjs.com/package/postgres) library.
- *
- * For more information, see the [`postgresIntegration` documentation](https://docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/postgres/).
- *
- * @example
- * ```javascript
- * const Sentry = require('@sentry/node');
- *
- * Sentry.init({
- *  integrations: [Sentry.postgresJsIntegration()],
- * });
- * ```
- */
-export declare const postgresJsIntegration: (options?: PostgresJsInstrumentationConfig | undefined) => import("@sentry/core").Integration & {
-    name: "PostgresJs";
-};
-export {};
-//# sourceMappingURL=postgresjs.d.ts.map

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

@@ -1,22 +0,0 @@
-import { IORedisResponseCustomAttributeFunction } from './vendored/types';
-export 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;
-/** Set the options consumed by {@link cacheResponseHook}. */
-export declare function setRedisOptions(options: RedisOptions): void;
-export declare const cacheResponseHook: IORedisResponseCustomAttributeFunction;
-//# sourceMappingURL=cache.d.ts.map

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

@@ -1,28 +0,0 @@
-import { RedisOptions } from './cache';
-export { _redisOptions, cacheResponseHook } from './cache';
-/**
- * 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: "Redis";
-};
-/**
- * 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 & {
-    name: "Redis";
-};
-//# sourceMappingURL=index.d.ts.map

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

@@ -1,10 +0,0 @@
-import { InstrumentationBase, InstrumentationNodeModuleDefinition } from '@opentelemetry/instrumentation';
-import { IORedisInstrumentationConfig } from './types';
-export declare class IORedisInstrumentation extends InstrumentationBase<IORedisInstrumentationConfig> {
-    constructor(config?: IORedisInstrumentationConfig);
-    protected init(): InstrumentationNodeModuleDefinition[];
-    private _patchSendCommand;
-    private _patchConnection;
-    private _callResponseHook;
-}
-//# sourceMappingURL=ioredis-instrumentation.d.ts.map

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

@@ -1,16 +0,0 @@
-import { TracerProvider } from '@opentelemetry/api';
-import { InstrumentationBase } from '@opentelemetry/instrumentation';
-import { RedisInstrumentationConfig } from './types';
-export declare class RedisInstrumentation extends InstrumentationBase<RedisInstrumentationConfig> {
-    private instrumentationV2_V3;
-    private instrumentationV4_V5;
-    private initialized;
-    constructor(config?: RedisInstrumentationConfig);
-    setConfig(config?: RedisInstrumentationConfig): void;
-    init(): void;
-    getModuleDefinitions(): import("@opentelemetry/instrumentation").InstrumentationModuleDefinition[];
-    setTracerProvider(tracerProvider: TracerProvider): void;
-    enable(): void;
-    disable(): void;
-}
-//# sourceMappingURL=redis-instrumentation.d.ts.map

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

@@ -1,4 +0,0 @@
-export declare const ATTR_DB_CONNECTION_STRING = "db.connection_string";
-export declare const DB_SYSTEM_NAME_VALUE_REDIS = "redis";
-export declare const DB_SYSTEM_VALUE_REDIS = "redis";
-//# sourceMappingURL=semconv.d.ts.map

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

@@ -1,24 +0,0 @@
-import { Span } from '@sentry/core';
-import { InstrumentationConfig } from '@opentelemetry/instrumentation';
-/**
- * Function that can be used to add custom attributes to span on response from redis server
- */
-export interface RedisResponseCustomAttributeFunction {
-    (span: Span, cmdName: string, cmdArgs: Array<string | Buffer>, response: unknown): void;
-}
-export interface RedisInstrumentationConfig extends InstrumentationConfig {
-    /** Function for adding custom attributes on db response */
-    responseHook?: RedisResponseCustomAttributeFunction;
-}
-export type CommandArgs = Array<string | Buffer | number | any[]>;
-/**
- * Function that can be used to add custom attributes to span on response from redis server (ioredis)
- */
-export interface IORedisResponseCustomAttributeFunction {
-    (span: Span, cmdName: string, cmdArgs: CommandArgs, response: unknown): void;
-}
-export interface IORedisInstrumentationConfig extends InstrumentationConfig {
-    /** Function for adding custom attributes on db response */
-    responseHook?: IORedisResponseCustomAttributeFunction;
-}
-//# sourceMappingURL=types.d.ts.map

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

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

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

@@ -1,11 +0,0 @@
-import { InstrumentationConfig } from '@opentelemetry/instrumentation';
-import { InstrumentationBase, InstrumentationNodeModuleDefinition } from '@opentelemetry/instrumentation';
-export declare class TediousInstrumentation extends InstrumentationBase<InstrumentationConfig> {
-    static readonly COMPONENT = "tedious";
-    constructor(config?: InstrumentationConfig);
-    protected init(): InstrumentationNodeModuleDefinition[];
-    private _patchConnect;
-    private _patchQuery;
-    private _patchCallbackQuery;
-}
-//# sourceMappingURL=instrumentation.d.ts.map

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

@@ -1,19 +0,0 @@
-/**
- * Deprecated, use `db.collection.name` instead.
- *
- * @example "mytable"
- *
- * @experimental This attribute is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`.
- *
- * @deprecated Replaced by `db.collection.name`, but only if not extracting the value from `db.query.text`.
- */
-export declare const ATTR_DB_SQL_TABLE: "db.sql.table";
-/**
- * Enum value "mssql" for attribute `db.system`.
- *
- * Microsoft SQL Server
- *
- * @experimental This enum value is experimental and is subject to breaking changes in minor releases of `@opentelemetry/semantic-conventions`.
- */
-export declare const DB_SYSTEM_VALUE_MSSQL: "mssql";
-//# sourceMappingURL=semconv.d.ts.map

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

@@ -1,21 +0,0 @@
-import { EventEmitter } from 'events';
-export declare class Connection extends EventEmitter {
-    config: any;
-    connect(connectListener?: (err?: Error) => void): void;
-    execSql(request: Request): void;
-    [key: string]: any;
-}
-export declare class Request extends EventEmitter {
-    sqlTextOrProcedure: string | undefined;
-    callback: any;
-    table: string | undefined;
-    parametersByName: any;
-    constructor(sqlTextOrProcedure: string | undefined, callback: (error: Error | null | undefined, rowCount?: number, rows?: any) => void);
-    addParameter(name: string, type: any, value?: unknown, options?: any): void;
-    [key: string]: any;
-}
-export declare const TYPES: {
-    VarBinary: any;
-    [key: string]: any;
-};
-//# sourceMappingURL=tedious-types.d.ts.map

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

@@ -1,9 +0,0 @@
-/**
- * The span name SHOULD be set to a low cardinality value
- * representing the statement executed on the database.
- *
- * @returns Operation executed on Tedious Connection. Does not map to SQL statement in any way.
- */
-export declare function getSpanName(operation: string, db: string | undefined, sql: string | undefined, bulkLoadTable: string | undefined): string;
-export declare const once: (fn: Function) => (...args: unknown[]) => any;
-//# sourceMappingURL=utils.d.ts.map

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

@@ -1,2 +0,0 @@
-export declare const INTEGRATION_NAME: "VercelAI";
-//# sourceMappingURL=constants.d.ts.map

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

@@ -1,44 +0,0 @@
-import { SentryVercelAiInstrumentation } from './instrumentation';
-import { VercelAiOptions } from './types';
-export declare const instrumentVercelAi: ((options?: unknown) => SentryVercelAiInstrumentation) & {
-    id: string;
-};
-/**
- * Adds Sentry tracing instrumentation for the [ai](https://www.npmjs.com/package/ai) library.
- *
- * For more information, see the [`ai` documentation](https://sdk.vercel.ai/docs/ai-sdk-core/telemetry).
- *
- * @example
- * ```javascript
- * const Sentry = require('@sentry/node');
- *
- * Sentry.init({
- *  integrations: [Sentry.vercelAIIntegration()],
- * });
- * ```
- *
- * This integration adds tracing support to all `ai` function calls.
- * You need to opt-in to collecting spans for a specific call,
- * you can do so by setting `experimental_telemetry.isEnabled` to `true` in the first argument of the function call.
- *
- * ```javascript
- * const result = await generateText({
- *   model: openai('gpt-4-turbo'),
- *   experimental_telemetry: { isEnabled: true },
- * });
- * ```
- *
- * If you want to collect inputs and outputs for a specific call, you must specifically opt-in to each
- * function call by setting `experimental_telemetry.recordInputs` and `experimental_telemetry.recordOutputs`
- * to `true`.
- *
- * ```javascript
- * const result = await generateText({
- *  model: openai('gpt-4-turbo'),
- *  experimental_telemetry: { isEnabled: true, recordInputs: true, recordOutputs: true },
- * });
- */
-export declare const vercelAIIntegration: (options?: VercelAiOptions | undefined) => import("@sentry/core").Integration & {
-    name: "VercelAI";
-};
-//# sourceMappingURL=index.d.ts.map

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

@@ -1,56 +0,0 @@
-import { InstrumentationConfig, InstrumentationModuleDefinition } from '@opentelemetry/instrumentation';
-import { InstrumentationBase } from '@opentelemetry/instrumentation';
-interface RecordingOptions {
-    recordInputs?: boolean;
-    recordOutputs?: boolean;
-}
-/**
- * Process tool call results: capture tool errors and clean up span context mappings.
- *
- * Error checking runs first (needs span context for linking), then cleanup removes all entries.
- * Tool errors are not rejected in Vercel AI V5 — they appear as metadata in the result content.
- */
-export declare function processToolCallResults(result: unknown): void;
-/**
- * Remove span context entries for all completed tool calls in the content array.
- */
-export declare function cleanupToolCallSpanContexts(content: Array<object>): void;
-/**
- * Determines whether to record inputs and outputs for Vercel AI telemetry based on the configuration hierarchy.
- *
- * The order of precedence is:
- * 1. The vercel ai integration options
- * 2. The experimental_telemetry options in the vercel ai method calls
- * 3. When telemetry is explicitly enabled (isEnabled: true), default to recording
- * 4. Otherwise, use the dataCollection.genAI settings from client options
- */
-export declare function determineRecordingSettings(integrationRecordingOptions: RecordingOptions | undefined, methodTelemetryOptions: RecordingOptions, telemetryExplicitlyEnabled: boolean | undefined, defaultInputsEnabled: boolean, defaultOutputsEnabled: boolean): {
-    recordInputs: boolean;
-    recordOutputs: boolean;
-};
-/**
- * This detects is added by the Sentry Vercel AI Integration to detect if the integration should
- * be enabled.
- *
- * It also patches the `ai` module to enable Vercel AI telemetry automatically for all methods.
- */
-export declare class SentryVercelAiInstrumentation extends InstrumentationBase {
-    private _isPatched;
-    private _callbacks;
-    constructor(config?: InstrumentationConfig);
-    /**
-     * Initializes the instrumentation by defining the modules to be patched.
-     */
-    init(): InstrumentationModuleDefinition;
-    /**
-     * Call the provided callback when the module is patched.
-     * If it has already been patched, the callback will be called immediately.
-     */
-    callWhenPatched(callback: () => void): void;
-    /**
-     * Patches module exports to enable Vercel AI telemetry.
-     */
-    private _patch;
-}
-export {};
-//# sourceMappingURL=instrumentation.d.ts.map

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

@@ -1,50 +0,0 @@
-import { Integration } from '@sentry/core';
-import { VercelAiOptions as VercelAiBaseOptions } from '@sentry/server-utils';
-/**
- * Telemetry configuration.
- */
-export type TelemetrySettings = {
-    /**
-     * Enable or disable telemetry. Disabled by default while experimental.
-     */
-    isEnabled?: boolean;
-    /**
-     * Enable or disable input recording. Enabled by default.
-     *
-     * You might want to disable input recording to avoid recording sensitive
-     * information, to reduce data transfers, or to increase performance.
-     */
-    recordInputs?: boolean;
-    /**
-     * Enable or disable output recording. Enabled by default.
-     *
-     * You might want to disable output recording to avoid recording sensitive
-     * information, to reduce data transfers, or to increase performance.
-     */
-    recordOutputs?: boolean;
-    /**
-     * Identifier for this function. Used to group telemetry data by function.
-     */
-    functionId?: string;
-    /**
-     * Additional information to include in the telemetry data.
-     */
-    metadata?: Record<string, AttributeValue>;
-};
-/**
- * Attribute values may be any non-nullish primitive value except an object.
- *
- * null or undefined attribute values are invalid and will result in undefined behavior.
- */
-export declare type AttributeValue = string | number | boolean | Array<null | undefined | string> | Array<null | undefined | number> | Array<null | undefined | boolean>;
-export interface VercelAiOptions extends VercelAiBaseOptions {
-    /**
-     * By default, the instrumentation will register span processors only when the ai package is used.
-     * If you want to register the span processors even when the ai package usage cannot be detected, you can set `force` to `true`.
-     */
-    force?: boolean;
-}
-export interface VercelAiIntegration extends Integration {
-    options: VercelAiOptions;
-}
-//# sourceMappingURL=types.d.ts.map

package/build/types-ts3.8/preload.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=preload.d.ts.map

package/build/types-ts3.8/sdk/diagnosticsChannelInjection.d.ts

@@ -1,41 +0,0 @@
-import { Integration } from '@sentry/core';
-/**
- * The orchestrion-driven pieces, resolved lazily by the opt-in loader.
- *
- * IMPORTANT: this module (and everything `init()` imports) must NOT reference
- * the orchestrion code (`@sentry/server-utils/orchestrion/*`). The only
- * reference lives inside `experimentalUseDiagnosticsChannelInjection()` (a
- * separate module, reachable solely through that public export). That's the
- * tree-shaking boundary: if an app never calls the opt-in function, then a
- * bundler drops the entire orchestrion subtree, including its transitive
- * dependencies, while an app that does call it gets it bundled
- * normally.
- */
-export interface DiagnosticsChannelInjection {
-    /** Channel-based integrations to register, replacing their OTel equivalents. */
-    integrations: Integration[] | readonly Integration[];
-    /** OTel integration names these replace; filtered out of the default set. */
-    replacedOtelIntegrationNames: string[];
-    /** Installs the module hooks that inject the diagnostics channels. */
-    register: () => void;
-    /** Warns (DEBUG only) about missing or doubled channel injection. */
-    detect: () => void;
-}
-/**
- * Set by `experimentalUseDiagnosticsChannelInjection()`. The loader
- * is the only thing that pulls in the orchestrion modules; see
- * {@link DiagnosticsChannelInjection) re tree-shaking concerns this addresses.
- *
- * @internal
- */
-export declare function setDiagnosticsChannelInjectionLoader(load: () => DiagnosticsChannelInjection): void;
-/** Whether `experimentalUseDiagnosticsChannelInjection()` was called. */
-export declare function isDiagnosticsChannelInjectionEnabled(): boolean;
-/**
- * Resolve and memoize the orchestrion pieces. This is what actually loads
- * the orchestrion modules. Returns `undefined` if the app never opted in.
- * Callers gate this on span recording, so the modules load only when both
- * opted in and tracing is enabled.
- */
-export declare function resolveDiagnosticsChannelInjection(): DiagnosticsChannelInjection | undefined;
-//# sourceMappingURL=diagnosticsChannelInjection.d.ts.map