@sentry/node 9.32.0 → 9.34.0-alpha.1

package/build/types-ts3.8/utils/errorhandling.d.ts

@@ -1,5 +0,0 @@
-/**
- * @hidden
- */
-export declare function logAndExitProcess(error: unknown): void;
-//# sourceMappingURL=errorhandling.d.ts.map

package/build/types-ts3.8/utils/getRequestUrl.d.ts

@@ -1,5 +0,0 @@
-/// <reference types="node" />
-import { RequestOptions } from 'node:http';
-/** Build a full URL from request options. */
-export declare function getRequestUrl(requestOptions: RequestOptions): string;
-//# sourceMappingURL=getRequestUrl.d.ts.map

package/build/types-ts3.8/utils/module.d.ts

@@ -1,3 +0,0 @@
-/** Creates a function that gets the module name from a filename */
-export declare function createGetModuleFromFilename(basePath?: string, isWindows?: boolean): (filename: string | undefined) => string | undefined;
-//# sourceMappingURL=module.d.ts.map

package/build/types-ts3.8/utils/prepareEvent.d.ts

@@ -1,17 +0,0 @@
-import { CaptureContext, EventHint, ScopeContext } from '@sentry/core';
-/**
- * This type makes sure that we get either a CaptureContext, OR an EventHint.
- * It does not allow mixing them, which could lead to unexpected outcomes, e.g. this is disallowed:
- * { user: { id: '123' }, mechanism: { handled: false } }
- */
-export type ExclusiveEventHintOrCaptureContext = (CaptureContext & Partial<{
-    [key in keyof EventHint]: never;
-}>) | (EventHint & Partial<{
-    [key in keyof ScopeContext]: never;
-}>);
-/**
- * Parse either an `EventHint` directly, or convert a `CaptureContext` to an `EventHint`.
- * This is used to allow to update method signatures that used to accept a `CaptureContext` but should now accept an `EventHint`.
- */
-export declare function parseEventHintOrCaptureContext(hint: ExclusiveEventHintOrCaptureContext | undefined): EventHint | undefined;
-//# sourceMappingURL=prepareEvent.d.ts.map