Files
klz-cables.com/.pnpm-store/v10/files/ed/418681c157e8ac4e63963b1b6731f9a5f785d4c18675a0288ed2dad97a25c7c818d32dbe7836a577b9ab3e1465c53cf944697d016d1babc1501f3a1f6eff1d
Marc Mintel 5397309103
Some checks failed
Build & Deploy / 🔍 Prepare (push) Successful in 20s
Build & Deploy / 🧪 QA (push) Failing after 34s
Build & Deploy / 🏗️ Build (push) Has started running
Build & Deploy / 🚀 Deploy (push) Has been cancelled
Build & Deploy / 🧪 Smoke Test (push) Has been cancelled
Build & Deploy / ⚡ Lighthouse (push) Has been cancelled
Build & Deploy / 🔔 Notify (push) Has been cancelled
fix(products): fix breadcrumbs and product filtering (backport from main)
2026-02-24 16:04:21 +01:00

76 lines
3.1 KiB
Plaintext

import { ClientOptions, Options, TracePropagationTargets } from '@sentry/core';
import { VercelEdgeClient } from './client';
import { VercelEdgeTransportOptions } from './transports';
export interface BaseVercelEdgeOptions {
/**
* List of strings/regex controlling to which outgoing requests
* the SDK will attach tracing headers.
*
* By default the SDK will attach those headers to all outgoing
* requests. If this option is provided, the SDK will match the
* request URL of outgoing requests against the items in this
* array, and only attach tracing headers if a match was found.
*
* @example
* ```js
* Sentry.init({
* tracePropagationTargets: ['api.site.com'],
* });
* ```
*/
tracePropagationTargets?: TracePropagationTargets;
/** Sets an optional server name (device name) */
serverName?: string;
/**
* Override the runtime name reported in events.
* Defaults to 'vercel-edge' if not specified.
*
* @hidden This is primarily used internally to support platforms like OpenNext/Cloudflare.
*/
runtime?: {
name: string;
version?: string;
};
/**
* Specify a custom VercelEdgeClient to be used. Must extend VercelEdgeClient!
* This is not a public, supported API, but used internally only.
*
* @hidden
* */
clientClass?: typeof VercelEdgeClient;
/**
* If this is set to true, the SDK will not set up OpenTelemetry automatically.
* In this case, you _have_ to ensure to set it up correctly yourself, including:
* * The `SentrySpanProcessor`
* * The `SentryPropagator`
* * The `SentryContextManager`
* * The `SentrySampler`
*/
skipOpenTelemetrySetup?: boolean;
/**
* The max. duration in seconds that the SDK will wait for parent spans to be finished before discarding a span.
* The SDK will automatically clean up spans that have no finished parent after this duration.
* This is necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing.
* However, if you have very long-running spans in your application, a shorter duration might cause spans to be discarded too early.
* In this case, you can increase this duration to a value that fits your expected data.
*
* Defaults to 300 seconds (5 minutes).
*/
maxSpanWaitDuration?: number;
/** Callback that is executed when a fatal global error occurs. */
onFatalError?(this: void, error: Error): void;
}
/**
* Configuration options for the Sentry VercelEdge SDK
* @see @sentry/core Options for more information.
*/
export interface VercelEdgeOptions extends Options<VercelEdgeTransportOptions>, BaseVercelEdgeOptions {
}
/**
* Configuration options for the Sentry VercelEdge SDK Client class
* @see VercelEdgeClient for more information.
*/
export interface VercelEdgeClientOptions extends ClientOptions<VercelEdgeTransportOptions>, BaseVercelEdgeOptions {
}
//# sourceMappingURL=types.d.ts.map