cloudflare-next-intl 0.6.4 → 0.6.6

package/dist/types/config/intl_sitemap.d.ts

@@ -1,8 +0,0 @@
-import type { MetadataRoute } from 'next';
-import type { IntlSitemap } from '../types/types';
-declare function generateIntlSitemapIml({ intlSitemap, url }: {
-    intlSitemap: IntlSitemap[];
-    url: string;
-}): MetadataRoute.Sitemap;
-declare const generateIntlSitemap: typeof generateIntlSitemapIml;
-export default generateIntlSitemap;

package/dist/types/config/intl_sitemap.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/config/middleware.bench.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/config/middleware.d.ts

@@ -1,21 +0,0 @@
-import type { NextRequest } from 'next/server';
-import { NextResponse } from 'next/server';
-import type { MiddlewareCustomHandler } from '../types/types';
-export declare const localesSet: Set<string>;
-/**
- * This middleware function runs for every incoming request. Handles locale
- * detection/routing, then optionally defers to your own custom logic.
- *
- * @param request The incoming request (pass through from your `middleware.ts`).
- * @param options.middlewareHandler  Your own logic (auth, feature flags, etc.),
- *   run alongside locale routing — see {@link MiddlewareCustomHandler} for the
- *   full contract (`rewriteUrl` / `redirectUrl` and what to return).
- * @param options.runHandlerOnRedirect  By default, `middlewareHandler` does
- *   NOT run for the locale-redirect case (so it never receives a
- *   `redirectUrl`). Set to `true` to also run it on redirects.
- *   Defaults to `false`.
- */
-export default function intlMiddleware(request: NextRequest, options?: {
-    middlewareHandler?: MiddlewareCustomHandler;
-    runHandlerOnRedirect?: boolean;
-}): Promise<NextResponse<unknown>>;

package/dist/types/config/middleware.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/cookie_consent/client/components/clarity_script.d.ts

@@ -1,10 +0,0 @@
-/**
- * Loads and initializes Microsoft Clarity. Split into its own module and
- * loaded via `next/dynamic` from `cookie_consent_analytics.tsx` so it's
- * only fetched as a separate chunk once actually rendered (consent granted
- * and `analytics.clarityProjectId` set) — `@microsoft/clarity` is a real
- * dependency of this package, so it's always installed regardless.
- */
-export default function ClarityScript({ projectId }: {
-    projectId: string;
-}): null;

package/dist/types/cookie_consent/client/components/cookie_consent_analytics.bench.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/cookie_consent/client/components/cookie_consent_analytics.d.ts

@@ -1,19 +0,0 @@
-import type { CookieConsentAnalyticsConfig } from '../../../types/types';
-/**
- * Renders whichever analytics/ads scripts have a resolved secret, gated on
- * consent: Google Consent Mode bootstrap always loads (defaults to
- * `denied`, only sends `update` once `consent` is decided); Cloudflare Web
- * Analytics beacon and Microsoft Clarity only load once `consent === true`.
- * Rendered automatically by `IntlProvider` when `cookieConsent.analytics`/
- * `getAnalytics` resolves at least one field and `autoWireAnalytics` isn't
- * `false` — render manually instead if you set `autoWireAnalytics: false`.
- */
-export default function CookieConsentAnalytics({ config }: {
-    config: CookieConsentAnalyticsConfig;
-}): React.ReactElement | null;
-/**
- * Denies storage by default and loads the configured Google tags; the
- * effect above sends the `update` once consent is known. Only IDs present
- * in `config` are included.
- */
-export declare function googleConsentModeBootstrapScript(config: CookieConsentAnalyticsConfig): string;

package/dist/types/cookie_consent/client/components/cookie_consent_dialog.d.ts

@@ -1,35 +0,0 @@
-import type { ConsentValue, CookieDialogClassNames, CookieDialogStyles } from '../../types';
-export interface CookieConsentDialogProps {
-    /** Banner message text. */
-    message?: React.ReactNode;
-    /**
-     * Link element rendered right after `message`. Defaults to a link to
-     * `cookieConsent.privacyPolicyPath` (`'/privacy-policy'` unless
-     * configured otherwise) with `privacyPolicyLinkText` as its label. Pass
-     * `null` to render no link, or your own element to override it.
-     */
-    link?: React.ReactNode;
-    /** Label for the default privacy-policy link. Ignored when `link` is set. */
-    privacyPolicyLinkText?: string;
-    acceptText?: string;
-    declineText?: string;
-    /** Hides the decline ("necessary only") button, leaving only accept. */
-    hideDecline?: boolean;
-    id?: string;
-    classNames?: CookieDialogClassNames;
-    styles?: CookieDialogStyles;
-    /**
-     * Full custom render — receives the resolved consent state/actions and
-     * bypasses the default markup entirely. Use for a fully bespoke dialog.
-     */
-    render?: (props: {
-        setConsent: (value: ConsentValue) => void;
-    }) => React.ReactNode;
-}
-/**
- * Cookie-consent banner. Renders `null` once `consent` is already decided.
- * Every visual aspect is overridable via `classNames`/`styles` (per-slot) or
- * `render` (full custom markup) — none of it is hardcoded to Tailwind or any
- * particular design system.
- */
-export default function CookieConsentDialog({ message, link, privacyPolicyLinkText, acceptText, declineText, hideDecline, id, classNames, styles, render, }: CookieConsentDialogProps): React.ReactElement | null;

package/dist/types/cookie_consent/client/components/default_dialog_styles.d.ts

@@ -1,2 +0,0 @@
-import type { CookieDialogClassNames } from '../../types';
-export declare const defaultCookieDialogClassNames: CookieDialogClassNames;

package/dist/types/cookie_consent/client/components/default_dialog_text.d.ts

@@ -1,13 +0,0 @@
-export interface CookieConsentDefaultText {
-    message: string;
-    privacyPolicyLinkText: string;
-    acceptText: string;
-    declineText: string;
-}
-export interface PrivacyPolicyUpdateDefaultText {
-    message: string;
-    privacyPolicyLinkText: string;
-    closeText: string;
-}
-export declare const defaultCookieConsentText: Record<string, CookieConsentDefaultText>;
-export declare const defaultPrivacyPolicyUpdateText: Record<string, PrivacyPolicyUpdateDefaultText>;

package/dist/types/cookie_consent/client/components/default_privacy_policy_link.d.ts

@@ -1,14 +0,0 @@
-/**
- * Renders the default privacy-policy link used by `CookieConsentDialog`/
- * `PrivacyPolicyUpdateDialog` when their `link` prop is omitted. Returns
- * `null` when `privacyPolicyPath` is `false` (disabled via
- * `cookieConsent.privacyPolicyPath`). Locale-prefixes `privacyPolicyPath`
- * the same way the server `Link` component does — reads the locale set by
- * `LocationzationClientProvider` on the current render.
- */
-export default function DefaultPrivacyPolicyLink({ privacyPolicyPath, text, className, style }: {
-    privacyPolicyPath: string | false;
-    text: string;
-    className?: string;
-    style?: React.CSSProperties;
-}): React.ReactElement | null;

package/dist/types/cookie_consent/client/components/dialog_portal.d.ts

@@ -1,11 +0,0 @@
-/**
- * Renders `children` into `document.body` via a portal, so the default
- * dialogs always stack on top of the host app regardless of its own
- * stacking contexts (a `z-index` alone can't escape an ancestor with
- * `transform`/`filter`/`opacity`/`isolation`, all common in app shells).
- * Only called client-side (both dialogs already gate on `isMounted`), so
- * `document` is always defined here.
- */
-export default function DialogPortal({ children }: {
-    children: React.ReactNode;
-}): React.ReactPortal;

package/dist/types/cookie_consent/client/components/privacy_policy_update_dialog.d.ts

@@ -1,31 +0,0 @@
-import type { CookieDialogClassNames, CookieDialogStyles } from '../../types';
-export interface PrivacyPolicyUpdateDialogProps {
-    message?: React.ReactNode;
-    /**
-     * Link element rendered right after `message`. Defaults to a link to
-     * `cookieConsent.privacyPolicyPath` (`'/privacy-policy'` unless
-     * configured otherwise) with `privacyPolicyLinkText` as its label. Pass
-     * `null` to render no link, or your own element to override it.
-     */
-    link?: React.ReactNode;
-    /** Label for the default privacy-policy link. Ignored when `link` is set. */
-    privacyPolicyLinkText?: string;
-    closeText?: string;
-    id?: string;
-    classNames?: CookieDialogClassNames;
-    styles?: CookieDialogStyles;
-    /**
-     * Full custom render — receives the acknowledge action and bypasses the
-     * default markup entirely.
-     */
-    render?: (props: {
-        acknowledge: () => void;
-    }) => React.ReactNode;
-}
-/**
- * "Privacy policy updated" banner. Auto-enabled only when
- * `cookieConsent.privacyPolicyDate` is set on the `RoutingConfig` — renders
- * `null` otherwise, or once acknowledged. Every visual aspect is overridable
- * via `classNames`/`styles` (per-slot) or `render` (full custom markup).
- */
-export default function PrivacyPolicyUpdateDialog({ message, link, privacyPolicyLinkText, closeText, id, classNames, styles, render, }: PrivacyPolicyUpdateDialogProps): React.ReactElement | null;

package/dist/types/cookie_consent/client/cookie_consent_provider.bench.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/cookie_consent/client/cookie_consent_provider.d.ts

@@ -1,39 +0,0 @@
-import type { CookieConsentContextType } from '../types';
-export declare const CookieConsentContext: import("react").Context<CookieConsentContextType | null>;
-/**
- * Provides cookie-consent + privacy-policy-update state to
- * `useCookieConsent()` and the default `CookieConsentDialog`/
- * `PrivacyPolicyUpdateDialog` components. Requires `cookieConsent` to be set
- * on the `RoutingConfig` passed to `setIntlConfig` — throws a descriptive
- * error otherwise.
- *
- * The privacy-policy-update banner turns on automatically, and only when
- * `cookieConsent.privacyPolicyDate` is configured: once a visitor has
- * consented, if their stored consent date predates `privacyPolicyDate`,
- * `privacyPolicyUpdated` becomes `true` until they call
- * `acknowledgePrivacyPolicyUpdate()` — or until they navigate to
- * `cookieConsent.privacyPolicyPath`, which auto-acknowledges it (visiting
- * the page counts as having seen the update; skipped entirely when
- * `privacyPolicyPath` is `false`).
- *
- * @param requiresConsent Resolved server-side from
- *   `cookieConsent.getCountryCode`/`gdprCountries` — `false` means the
- *   visitor's country doesn't require the banner at all, so a first-time
- *   visitor (no stored cookie) gets `consent` seeded to `true` instead of
- *   `null`, skipping the dialog and unlocking analytics immediately.
- *   Defaults to `true` (always show the banner) when omitted, e.g. when
- *   `cookieConsent.getCountryCode` isn't configured.
- *
- * @example
- * ```tsx
- * <CookieConsentProvider>
- *   {children}
- *   <CookieConsentDialog />
- *   <PrivacyPolicyUpdateDialog />
- * </CookieConsentProvider>
- * ```
- */
-export default function CookieConsentProvider({ requiresConsent, children }: {
-    requiresConsent?: boolean;
-    children: React.ReactNode;
-}): React.ReactElement;

package/dist/types/cookie_consent/client/use_cookie_consent.d.ts

@@ -1,6 +0,0 @@
-import type { CookieConsentContextType } from '../types';
-/**
- * Reads cookie-consent + privacy-policy-update state. Must be called within
- * a `CookieConsentProvider`.
- */
-export default function useCookieConsent(): CookieConsentContextType;

package/dist/types/cookie_consent/gdpr_countries.bench.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/cookie_consent/gdpr_countries.d.ts

@@ -1,18 +0,0 @@
-import type { CookieConsentGetCloudflareContext, ErrorHandlingRoutingConfig } from '../types/types';
-/**
- * Default `cookieConsent.gdprCountries` — EU/EEA member states (GDPR),
- * Iceland/Liechtenstein/Norway (EEA), the UK (UK-GDPR), and Switzerland
- * (nFADP). ISO 3166-1 alpha-2.
- */
-export declare const defaultGdprCountries: readonly string[];
-/**
- * Resolves whether the cookie-consent banner is required for a visitor.
- *
- * - Neither getter set: fail-safe — consent is required by default since
- *   the visitor's country can't be determined at all.
- * - Either getter set: fail-safe — a country that couldn't be resolved
- *   still requires consent; only a resolved country OUTSIDE
- *   `gdprCountries` skips the banner. `getCountryCode` takes precedence
- *   over `getCloudflareContext` when both are set.
- */
-export default function resolveRequiresConsent(getCountryCode: (() => string | undefined | Promise<string | undefined>) | undefined, getCloudflareContext: CookieConsentGetCloudflareContext | undefined, gdprCountries: readonly string[] | undefined, errorHandlingConfig?: ErrorHandlingRoutingConfig): Promise<boolean>;

package/dist/types/cookie_consent/gdpr_countries.perf.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/cookie_consent/gdpr_countries.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/cookie_consent/index.d.ts

@@ -1,10 +0,0 @@
-export { default as CookieConsentProvider } from './client/cookie_consent_provider';
-export { default as useCookieConsent } from './client/use_cookie_consent';
-export { default as CookieConsentDialog } from './client/components/cookie_consent_dialog';
-export { default as PrivacyPolicyUpdateDialog } from './client/components/privacy_policy_update_dialog';
-export { default as CookieConsentAnalytics } from './client/components/cookie_consent_analytics';
-export { defaultGdprCountries } from './gdpr_countries';
-export type { CookieConsentContextType, ConsentValue, CookieDialogClassNames, CookieDialogStyles } from './types';
-export type { CookieConsentDialogProps } from './client/components/cookie_consent_dialog';
-export type { PrivacyPolicyUpdateDialogProps } from './client/components/privacy_policy_update_dialog';
-export type { CookieConsentRoutingConfig, CookieConsentAnalyticsConfig, CookieConsentCloudflareContext, CookieConsentGetCloudflareContext, } from '../types/types';

package/dist/types/cookie_consent/require_config.d.ts

@@ -1,7 +0,0 @@
-import type { CookieConsentRoutingConfig } from '../types/types';
-/**
- * Throws a descriptive error instead of silently no-op'ing when the
- * `cookie_consent` submodule is used without `cookieConsent` set on the
- * `RoutingConfig` passed to `setIntlConfig`.
- */
-export default function requireCookieConsentConfig(value: CookieConsentRoutingConfig | undefined): CookieConsentRoutingConfig;

package/dist/types/cookie_consent/require_config.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/cookie_consent/types.d.ts

@@ -1,57 +0,0 @@
-/** Consent value: `true` accepted, `false` necessary-only, `null` not yet decided. */
-export type ConsentValue = boolean | null;
-/** Context value returned by `useCookieConsent()`. */
-export interface CookieConsentContextType {
-    /** Current consent value; `null` until the visitor decides. */
-    consent: ConsentValue;
-    /**
-     * `false` until the client has read the stored consent/date cookies once
-     * (always `false` during SSR and the first client render, to avoid a
-     * hydration mismatch). The default dialog components render nothing
-     * until this is `true`, so a returning visitor's decided consent never
-     * flashes the banner before disappearing.
-     */
-    isMounted: boolean;
-    /**
-     * `true` once a privacy-policy update has been detected (stored consent
-     * predates `cookieConsent.privacyPolicyDate`) and hasn't been
-     * acknowledged yet. Always `false` when `privacyPolicyDate` is unset.
-     */
-    privacyPolicyUpdated: boolean;
-    /**
-     * Accepts (or rejects, with `false`) cookie consent and persists it.
-     * Pass `null` to clear the stored decision and reset `consent` back to
-     * `null`, so the default `CookieConsentDialog` banner reappears (e.g.
-     * for a "cookie settings" button).
-     */
-    setConsent: (value: ConsentValue) => void;
-    /** Acknowledges the privacy-policy update banner and persists the new date. */
-    acknowledgePrivacyPolicyUpdate: () => void;
-    /**
-     * Resolved from `cookieConsent.privacyPolicyPath` (defaults to
-     * `'/privacy-policy'`; `false` disables it). Used by the default
-     * dialog components to render a privacy-policy link automatically
-     * when their `link` prop is omitted.
-     */
-    privacyPolicyPath: string | false;
-}
-/** Slot-level style/class overrides accepted by the default dialog components. */
-export interface CookieDialogClassNames {
-    root?: string;
-    message?: string;
-    link?: string;
-    actions?: string;
-    acceptButton?: string;
-    declineButton?: string;
-    closeButton?: string;
-}
-/** Slot-level inline-style overrides accepted by the default dialog components. */
-export interface CookieDialogStyles {
-    root?: React.CSSProperties;
-    message?: React.CSSProperties;
-    link?: React.CSSProperties;
-    actions?: React.CSSProperties;
-    acceptButton?: React.CSSProperties;
-    declineButton?: React.CSSProperties;
-    closeButton?: React.CSSProperties;
-}

package/dist/types/error_handling/create_server_error_action.d.ts

@@ -1,19 +0,0 @@
-import type { ErrorHandlingParams } from '../types/types';
-import { type ReportErrorConfig } from './report_error';
-/**
- * Creates a `"use server"` action that reports a client-originated error via
- * `reportError`, so `config` (and anything it closes over — secrets,
- * `Secrets.telegramBotToken`-style env reads inside your `onError`) never
- * has to be imported into client-side code. Call this once (server-side,
- * e.g. next to your `RoutingConfig`) and pass the returned function to
- * client components that need to report an error — they only ever handle
- * the error value itself, never `config`.
- *
- * The error is stringified before crossing the client→server action
- * boundary (Next.js server actions serialize arguments; an `Error` instance
- * doesn't survive that intact) and `isClient: true` is set automatically.
- *
- * @param config Pass the relevant slices of your `RoutingConfig` directly —
- *   `{ errorHandling: config.errorHandling, generate: config.generate }`.
- */
-export default function createServerErrorAction(config: ReportErrorConfig | undefined): (error: unknown, classOrMethodName: string, params?: ErrorHandlingParams["params"]) => Promise<void>;

package/dist/types/error_handling/create_server_error_action.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/error_handling/default_ignored_console_errors.d.ts

@@ -1,13 +0,0 @@
-/**
- * Firebase Auth error codes this package's own `createLoginAction`/
- * `createSignUpAction`/`createForgotPasswordAction` already catch and
- * translate into a localized message (see
- * `firebase_auth/error_messages/firebase_auth_error_helper.ts`) — expected
- * user-input failures (wrong password, email already in use, etc.), not
- * bugs. They never reach `console.error`/`reportError` through this
- * package's own code; this list exists as defense-in-depth for consumers
- * whose own code logs one of these codes directly. Passing your own
- * `ignoreConsoleError` array replaces this default entirely — pass `[]` to
- * report everything.
- */
-export declare const defaultIgnoredConsoleErrors: readonly string[];

package/dist/types/error_handling/default_ignored_console_errors.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/error_handling/format_error_message.d.ts

@@ -1,9 +0,0 @@
-import type { ErrorHandlingParams } from '../types/types';
-/**
- * Builds a human-readable one-string summary of an `ErrorHandlingParams` —
- * `[classOrMethodName] Error: <message>` followed by non-empty `Params`/
- * `IsClient` sections. Never throws (`stringifyUnknown` is safe). Used as
- * `ErrorHandlingParams.formattedMessage` — read this instead of `error`/
- * `params` directly when you just want something printable.
- */
-export default function formatErrorMessage(params: ErrorHandlingParams): string;

package/dist/types/error_handling/format_error_message.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/error_handling/index.d.ts

@@ -1,9 +0,0 @@
-export { default as withErrorHandling } from './with_error_handling';
-export type { WithErrorHandlingOptions } from './with_error_handling';
-export { default as reportError } from './report_error';
-export type { ReportErrorConfig } from './report_error';
-export { default as installConsoleErrorOverride } from './install_console_error_override';
-export { default as stringifyUnknown } from './stringify_unknown';
-export { default as formatErrorMessage } from './format_error_message';
-export { defaultIgnoredConsoleErrors } from './default_ignored_console_errors';
-export type { ErrorHandlingParams, ErrorHandlingRoutingConfig } from '../types/types';

package/dist/types/error_handling/install_console_error_override.bench.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/error_handling/install_console_error_override.d.ts

@@ -1,29 +0,0 @@
-import { type ReportErrorConfig } from './report_error';
-/**
- * Replaces the global `console.error` so every `console.error(...)` call is
- * also routed through `config.errorHandling.onError`/`reportError` — the
- * original `console.error` still runs afterwards, nothing is swallowed.
- * Safe to call more than once (a no-op after the first call in this JS
- * realm — call it separately on the server and on the client, each has its
- * own `console`). Only takes effect when `config.errorHandling.overrideConsoleError`
- * is `true`.
- *
- * A component stuck in a render-error loop calls `console.error` on every
- * render — `reportError`'s own dedup/cap (on by default, see
- * `errorHandling.dedup`/`maxReports`) is what stops that from reporting
- * unboundedly; this function does not duplicate that cap itself.
- *
- * `config.errorHandling.ignoreConsoleErrors` (default
- * `defaultIgnoredConsoleErrors` — this package's own Firebase Auth error
- * codes for expected user-input failures) and `ignoreConsoleError` both
- * skip reporting a matching call while still logging it normally.
- *
- * @param config Pass the relevant slices of your `RoutingConfig` directly —
- *   `{ errorHandling: config.errorHandling, generate: config.generate }`.
- * @param isClient Passed through to every report's `ErrorHandlingParams.isClient`
- *   — set `true` when installing from client-side code (e.g. the client
- *   `LocationzationClientProvider`), omit/`false` on the server. There's no
- *   `getCloudflareContext`/`ctx.waitUntil` available in the browser, so
- *   client-side reports always await `onError` directly.
- */
-export default function installConsoleErrorOverride(config: ReportErrorConfig | undefined, isClient?: boolean): void;

package/dist/types/error_handling/install_console_error_override.perf.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/error_handling/install_console_error_override.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/error_handling/report_error.bench.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/error_handling/report_error.d.ts

@@ -1,40 +0,0 @@
-import type { ErrorHandlingParams, ErrorHandlingRoutingConfig, GenerateRoutingConfig } from '../types/types';
-export interface ReportErrorConfig {
-    errorHandling?: ErrorHandlingRoutingConfig;
-    generate?: GenerateRoutingConfig;
-}
-/**
- * Reports `params` via `config.errorHandling.onError` (default
- * `console.error(params.formattedMessage)`), unless
- * `config.errorHandling.enable === false`, `params.consent` is set and not
- * `true` (reporting to a third party without cookie consent can itself be
- * GDPR-relevant), or dedup throttles it (on by default — see
- * `errorHandling.dedup`/`throttleMs`/`resetDedup`). Never throws — a broken
- * reporter must not mask the original error.
- *
- * Always overwrites `params.formattedMessage` with a fresh
- * `formatErrorMessage(params)` before reporting — a human-readable one-line
- * summary (`[classOrMethodName] Error: <message>` plus non-empty sections)
- * instead of the raw `error`/`params` object, for a default reporter (or a
- * simple `onError`) to print directly.
- *
- * When `config.generate?.getCloudflareContext` is set, `waitUntil` is called
- * SYNCHRONOUSLY, in the same tick, with the `callOnError(...)` promise —
- * Cloudflare Workers only extends the request's lifetime for work already
- * registered with `waitUntil` by the time the handler returns; deferring
- * that call through an extra microtask (e.g. `Promise.resolve().then(...)`)
- * risks the isolate tearing down the request before `waitUntil` is ever
- * actually invoked, silently dropping the report. Falls back to awaiting
- * `onError` directly when `getCloudflareContext`/`ctx.waitUntil` is unset or
- * unavailable (e.g. outside a Cloudflare Worker).
- *
- * Passing `params.error` as `null`/`undefined` with `errorHandling.resetDedup: true`
- * and nothing else is a valid "reset-only" call: the dedup state clears and
- * `reportError` returns immediately, without calling `onError` — useful to
- * clear dedup state once at the very start of a request/cron tick, before
- * any handler that might call `reportError` for a real error runs.
- *
- * @param config Pass the relevant slices of your `RoutingConfig` directly —
- *   `{ errorHandling: config.errorHandling, generate: config.generate }`.
- */
-export default function reportError(config: ReportErrorConfig | undefined, params: ErrorHandlingParams): Promise<void>;

package/dist/types/error_handling/report_error.perf.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/error_handling/report_error.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/error_handling/stringify_unknown.bench.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/error_handling/stringify_unknown.d.ts

@@ -1,12 +0,0 @@
-/**
- * Safely converts an `unknown` value (typically `ErrorHandlingParams.error`)
- * into a string, for logging/dedup-keying/display — never throws.
- *
- * @param isClient Skips resolving function-wrapped/lazy error values on the
- *   client (matches `ErrorHandlingParams.isClient`) — running arbitrary
- *   caught functions client-side isn't safe the way it is on the server.
- * @param isNested Set when stringifying a value nested inside another
- *   object/array — falls back to a plain `JSON.stringify` (no pretty-print)
- *   so a single unserializable nested value can't crash the whole report.
- */
-export default function stringifyUnknown(value: unknown, isClient?: boolean, isNested?: boolean): string;

package/dist/types/error_handling/stringify_unknown.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/error_handling/with_error_handling.d.ts

@@ -1,15 +0,0 @@
-import type { ConsentValue } from '../cookie_consent/types';
-import { type ReportErrorConfig } from './report_error';
-export interface WithErrorHandlingOptions {
-    /** Pass the relevant slices of your `RoutingConfig` directly — `{ errorHandling: config.errorHandling, generate: config.generate }`. */
-    config?: ReportErrorConfig;
-    params?: unknown;
-    isClient?: boolean;
-    consent?: ConsentValue;
-}
-/**
- * Wraps `fn`, reporting (via `options.config`) then rethrowing any error it
- * throws or rejects with. Never swallows — callers keep their own
- * catch/fallback behavior, this only adds reporting on top.
- */
-export default function withErrorHandling<Args extends unknown[], Result>(fn: (...args: Args) => Result | Promise<Result>, classOrMethodName: string, options?: WithErrorHandlingOptions): (...args: Args) => Promise<Result>;

package/dist/types/error_handling/with_error_handling.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/firebase_auth/client/auth_actions.bench.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/firebase_auth/client/auth_actions.d.ts

@@ -1,46 +0,0 @@
-import type { AuthActionMessages, AuthFormState } from '../types';
-/**
- * Builds a login server action for React's `useActionState` form hook.
- * The returned function has the `(prevState, formData) => Promise<AuthFormState>`
- * shape `useActionState` expects — pass it directly as the action.
- *
- * `formData` must contain `email` and `password` fields.
- *
- * @param locale Used to localize the returned error message.
- * @param messages Localized action messages (currently unused by this action).
- * @returns A form action: `{ success: true }` on success, `{ error }` on failure.
- * @example
- * const [state, action] = useActionState(createLoginAction(locale, messages), {});
- * <form action={action}>...</form>
- */
-export declare function createLoginAction(locale: string, messages: AuthActionMessages): (_prevState: AuthFormState, formData: FormData) => Promise<AuthFormState>;
-/**
- * Builds a sign-up server action for React's `useActionState` form hook.
- * Same shape as {@link createLoginAction}.
- *
- * `formData` must contain `email`, `password`, and `confirmPassword` fields.
- *
- * @param locale Used to localize the returned error message.
- * @param messages `messages.mismatch` is returned as the error if
- *   `password` !== `confirmPassword`; other fields on `AuthActionMessages`
- *   are not read by this action.
- * @returns A form action: `{ success: true }` on success, `{ error }` on failure.
- * @example
- * const [state, action] = useActionState(createSignUpAction(locale, messages), {});
- * <form action={action}>...</form>
- */
-export declare function createSignUpAction(locale: string, messages: AuthActionMessages): (_prevState: AuthFormState, formData: FormData) => Promise<AuthFormState>;
-/**
- * Builds a forgot-password server action for React's `useActionState` form
- * hook. Same shape as {@link createLoginAction}.
- *
- * `formData` must contain an `email` field.
- *
- * @param locale Used to localize the returned error message.
- * @param messages Localized action messages (currently unused by this action).
- * @returns A form action: `{ success: true }` on success, `{ error }` on failure.
- * @example
- * const [state, action] = useActionState(createForgotPasswordAction(locale, messages), {});
- * <form action={action}>...</form>
- */
-export declare function createForgotPasswordAction(locale: string, messages: AuthActionMessages): (_prevState: AuthFormState, formData: FormData) => Promise<AuthFormState>;

package/dist/types/firebase_auth/client/auth_actions.test.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/firebase_auth/client/auth_user_cache.bench.d.ts

@@ -1 +0,0 @@
-export {};

package/dist/types/firebase_auth/client/auth_user_cache.d.ts

@@ -1,4 +0,0 @@
-import type { AuthUser } from '../types';
-export declare function setAuthUserCache(user: AuthUser | null): void;
-export declare function getAuthUserCache(): AuthUser | null;
-export declare function isAuthUserLoadingCache(): boolean;

package/dist/types/firebase_auth/client/auth_user_cache.test.d.ts

@@ -1 +0,0 @@
-export {};