@sentry/tanstackstart-react 10.70.0 → 11.0.0-alpha.1

package/build/types-ts3.8/vite/autoInstrumentMiddleware.d.ts

@@ -1,43 +0,0 @@
-import { Plugin } from 'vite';
-type AutoInstrumentMiddlewareOptions = {
-    enabled?: boolean;
-    debug?: boolean;
-};
-type WrapResult = {
-    code: string;
-    didWrap: boolean;
-    skipped: string[];
-};
-/**
- * Wraps global middleware arrays (requestMiddleware, functionMiddleware) in createStart() files.
- */
-export declare function wrapGlobalMiddleware(code: string, id: string, debug: boolean): WrapResult;
-/**
- * Wraps route middleware arrays in createFileRoute() files.
- */
-export declare function wrapRouteMiddleware(code: string, id: string, debug: boolean): WrapResult;
-/**
- * Wraps middleware arrays in createServerFn().middleware([...]) calls.
- */
-export declare function wrapServerFnMiddleware(code: string, id: string, debug: boolean): WrapResult;
-/**
- * A Vite plugin that automatically instruments TanStack Start middlewares:
- * - `requestMiddleware` and `functionMiddleware` arrays in `createStart()`
- * - `middleware` arrays in `createFileRoute()` route definitions
- */
-export declare function makeAutoInstrumentMiddlewarePlugin(options?: AutoInstrumentMiddlewareOptions): Plugin;
-/**
- * Convert array contents to object shorthand syntax.
- * e.g., "foo, bar, baz" → "{ foo, bar, baz }"
- *
- * Returns null if contents contain non-identifier expressions (function calls, etc.)
- * which cannot be converted to object shorthand.
- */
-export declare function arrayToObjectShorthand(contents: string): string | null;
-/**
- * Adds the wrapMiddlewaresWithSentry import to the code.
- * Handles 'use client' and 'use server' directives by inserting the import after them.
- */
-export declare function addSentryImport(code: string): string;
-export {};
-//# sourceMappingURL=autoInstrumentMiddleware.d.ts.map

package/build/types-ts3.8/vite/index.d.ts

@@ -1,4 +0,0 @@
-export { sentryTanstackStart } from './sentryTanstackStart';
-export { SentryTanstackStartOptions } from './sentryTanstackStart';
-export { TunnelRouteOptions } from './tunnelRoute';
-//# sourceMappingURL=index.d.ts.map

package/build/types-ts3.8/vite/routePatterns.d.ts

@@ -1,18 +0,0 @@
-import { Plugin } from 'vite';
-/**
- * Extracts route patterns from TanStack Start's generated routeTree.gen.ts
- * and replaces `__SENTRY_ROUTE_PATTERNS__` references with the extracted patterns.
- *
- * The route tree file is read during `transform` rather than `config` because
- * TanStack Start generates it during the build.
- */
-export declare function makeRoutePatternPlugin(): Plugin;
-/**
- * Extracts full route path patterns from the content of routeTree.gen.ts.
- *
- * Parses the `fullPaths` type union which contains the resolved full paths
- * (e.g., `fullPaths: '/' | '/page-a' | '/users/$userId'`).
- * This is more reliable than `path:` properties which can be relative for nested routes.
- */
-export declare function extractRoutePatterns(content: string): string[];
-//# sourceMappingURL=routePatterns.d.ts.map

package/build/types-ts3.8/vite/sentryTanstackStart.d.ts

@@ -1,79 +0,0 @@
-import { BuildTimeOptionsBase } from '@sentry/core';
-import { Plugin } from 'vite';
-import { TunnelRouteOptions } from './tunnelRoute';
-/**
- * Build-time options for the Sentry TanStack Start SDK.
- */
-export interface SentryTanstackStartOptions extends BuildTimeOptionsBase {
-    /**
-     * If this flag is `true`, the Sentry plugins will automatically instrument TanStack Start middlewares.
-     *
-     * This wraps global middlewares (`requestMiddleware` and `functionMiddleware`) in `createStart()` with Sentry
-     * instrumentation to capture performance data.
-     *
-     * Set to `false` to disable automatic middleware instrumentation if you prefer to wrap middlewares manually
-     * using `wrapMiddlewaresWithSentry`.
-     *
-     * @default true
-     */
-    autoInstrumentMiddleware?: boolean;
-    /**
-     * Options related to react component name annotations.
-     * Disabled by default, unless a value is set for this option.
-     * When enabled, your app's DOM will automatically be annotated during build-time with their respective component names.
-     * This will unlock the capability to search for Replays in Sentry by component name, as well as see component names in breadcrumbs and performance monitoring.
-     * Please note that this feature is not currently supported by the esbuild bundler plugins, and will only annotate React components
-     */
-    reactComponentAnnotation?: {
-        /**
-         * Whether the component name annotate plugin should be enabled or not.
-         */
-        enabled?: boolean;
-        /**
-         * A list of strings representing the names of components to ignore. The plugin will not apply `data-sentry` annotations on the DOM element for these components.
-         */
-        ignoredComponents?: string[];
-    };
-    /**
-     * Configures a framework-managed same-origin tunnel route for Sentry envelopes.
-     *
-     * This creates a TanStack Start server route backed by `createSentryTunnelRoute()` and applies the resulting path
-     * as the default `tunnel` option on the client.
-     *
-     * You can pass:
-     * - `true` to generate an opaque route path per dev session or production build.
-     * - `'/custom-path'` to use a fixed static route path.
-     * - `{ allowedDsns, path }` for full control. If `allowedDsns` is omitted or empty, the tunnel route derives the DSN
-     *   from the active server Sentry client at runtime.
-     *
-     * If you also pass `tunnel` to `Sentry.init()`, that explicit runtime option wins and a warning is emitted because
-     * the managed tunnel route is being bypassed.
-     */
-    tunnelRoute?: TunnelRouteOptions;
-}
-/**
- * Vite plugins for the Sentry TanStack Start SDK.
- *
- * @example
- * ```typescript
- * // vite.config.ts
- * import { defineConfig } from 'vite';
- * import { sentryTanstackStart } from '@sentry/tanstackstart-react/vite';
- * import { tanstackStart } from '@tanstack/react-start/plugin/vite';
- *
- * export default defineConfig({
- *   plugins: [
- *     tanstackStart(),
- *     sentryTanstackStart({
- *       org: 'your-org',
- *       project: 'your-project',
- *     }),
- *   ],
- * });
- * ```
- *
- * @param options - Options to configure the Sentry Vite plugins
- * @returns An array of Vite plugins
- */
-export declare function sentryTanstackStart(options?: SentryTanstackStartOptions): Plugin[];
-//# sourceMappingURL=sentryTanstackStart.d.ts.map

package/build/types-ts3.8/vite/sourceMaps.d.ts

@@ -1,27 +0,0 @@
-import { Plugin, UserConfig } from 'vite';
-import { SentryTanstackStartOptions } from './sentryTanstackStart';
-/**
- * A Sentry plugin for adding the @sentry/vite-plugin to automatically upload source maps to Sentry.
- */
-export declare function makeAddSentryVitePlugin(options: SentryTanstackStartOptions): Plugin[];
-/**
- * A Sentry plugin for TanStack Start React to enable "hidden" source maps if they are unset.
- */
-export declare function makeEnableSourceMapsVitePlugin(options: SentryTanstackStartOptions): Plugin[];
-/** There are 3 ways to set up source map generation (https://github.com/getsentry/sentry-javascript/issues/13993)
- *
- *     1. User explicitly disabled source maps
- *       - keep this setting (emit a warning that errors won't be unminified in Sentry)
- *       - We won't upload anything
- *
- *     2. Users enabled source map generation (true, 'hidden', 'inline').
- *       - keep this setting (don't do anything - like deletion - besides uploading)
- *
- *     3. Users didn't set source maps generation
- *       - we enable 'hidden' source maps generation
- *       - configure `filesToDeleteAfterUpload` to delete all .map files (we emit a log about this)
- *
- * --> only exported for testing
- */
-export declare function getUpdatedSourceMapSettings(viteConfig: UserConfig, sentryPluginOptions?: SentryTanstackStartOptions): boolean | 'inline' | 'hidden';
-//# sourceMappingURL=sourceMaps.d.ts.map

package/build/types-ts3.8/vite/tunnelRoute.d.ts

@@ -1,19 +0,0 @@
-import { Plugin } from 'vite';
-export type TunnelRouteOptions = true | string | {
-    /**
-     * A list of DSNs that are allowed to use the managed tunnel route.
-     *
-     * If omitted or empty, the tunnel route will derive the allowed DSN from the active server Sentry SDK at runtime.
-     */
-    allowedDsns?: string[];
-    /**
-     * Controls the public route path used by the managed tunnel route.
-     *
-     * If omitted, an opaque path is generated once per dev session or production build.
-     */
-    path?: string;
-};
-export declare function resolveTunnelRoute(tunnel: true | string): string;
-export declare function injectManagedTunnelRoute(source: string, resolvedTunnelRoute: string): string;
-export declare function makeTunnelRoutePlugin(options: TunnelRouteOptions, debug?: boolean): Plugin;
-//# sourceMappingURL=tunnelRoute.d.ts.map