@tanstack/preact-pacer 0.22.1 → 0.24.0

package/src/async-rate-limiter/useAsyncRateLimiter.ts

@@ -1,294 +0,0 @@
-import { useEffect, useMemo, useState } from 'preact/hooks'
-import { AsyncRateLimiter } from '@tanstack/pacer/async-rate-limiter'
-import { shallow, useSelector } from '@tanstack/preact-store'
-import { useDefaultPacerOptions } from '../provider/PacerProvider'
-import type { Store } from '@tanstack/preact-store'
-import type { AnyAsyncFunction } from '@tanstack/pacer/types'
-import type {
-  AsyncRateLimiterOptions,
-  AsyncRateLimiterState,
-} from '@tanstack/pacer/async-rate-limiter'
-import type { ComponentChildren } from 'preact'
-
-export interface PreactAsyncRateLimiterOptions<
-  TFn extends AnyAsyncFunction,
-  TSelected = {},
-> extends AsyncRateLimiterOptions<TFn> {
-  /**
-   * Optional callback invoked when the component unmounts. Receives the rate limiter instance.
-   * When provided, replaces the default cleanup (abort); use it to call reset(), add logging, etc.
-   */
-  onUnmount?: (rateLimiter: PreactAsyncRateLimiter<TFn, TSelected>) => void
-}
-
-export interface PreactAsyncRateLimiter<
-  TFn extends AnyAsyncFunction,
-  TSelected = {},
-> extends Omit<AsyncRateLimiter<TFn>, 'store'> {
-  /**
-   * A Preact HOC (Higher Order Component) that allows you to subscribe to the async rate limiter state.
-   *
-   * This is useful for opting into state re-renders for specific parts of the rate limiter state
-   * deep in your component tree without needing to pass a selector to the hook.
-   *
-   * @example
-   * <rateLimiter.Subscribe selector={(state) => ({ rejectionCount: state.rejectionCount })}>
-   *   {({ rejectionCount }) => (
-   *     <div>Rejections: {rejectionCount}</div>
-   *   )}
-   * </rateLimiter.Subscribe>
-   */
-  Subscribe: <TSelected>(props: {
-    selector: (state: AsyncRateLimiterState<TFn>) => TSelected
-    children: ((state: TSelected) => ComponentChildren) | ComponentChildren
-  }) => ComponentChildren
-  /**
-   * Reactive state that will be updated and re-rendered when the rate limiter state changes
-   *
-   * Use this instead of `rateLimiter.store.state`
-   */
-  readonly state: Readonly<TSelected>
-  /**
-   * @deprecated Use `rateLimiter.state` instead of `rateLimiter.store.state` if you want to read reactive state.
-   * The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.
-   * Although, you can make the state reactive by using the `useSelector` in your own usage.
-   */
-  readonly store: Store<Readonly<AsyncRateLimiterState<TFn>>>
-}
-
-/**
- * A low-level Preact hook that creates an `AsyncRateLimiter` instance to limit how many times an async function can execute within a time window.
- *
- * This hook is designed to be flexible and state-management agnostic - it simply returns a rate limiter instance that
- * you can integrate with any state management solution (useState, Redux, Zustand, Jotai, etc).
- *
- * Rate limiting allows an async function to execute up to a specified limit within a time window,
- * then blocks subsequent calls until the window passes. This is useful for respecting API rate limits,
- * managing resource constraints, or controlling bursts of async operations.
- *
- * Unlike the non-async RateLimiter, this async version supports returning values from the rate-limited function,
- * making it ideal for API calls and other async operations where you want the result of the `maybeExecute` call
- * instead of setting the result on a state variable from within the rate-limited function.
- *
- * The rate limiter supports two types of windows:
- * - 'fixed': A strict window that resets after the window period. All executions within the window count
- *   towards the limit, and the window resets completely after the period.
- * - 'sliding': A rolling window that allows executions as old ones expire. This provides a more
- *   consistent rate of execution over time.
- *
- * Error Handling:
- * - If an `onError` handler is provided, it will be called with the error and rate limiter instance
- * - If `throwOnError` is true (default when no onError handler is provided), the error will be thrown
- * - If `throwOnError` is false (default when onError handler is provided), the error will be swallowed
- * - Both onError and throwOnError can be used together - the handler will be called before any error is thrown
- * - The error state can be checked using the underlying AsyncRateLimiter instance
- * - Rate limit rejections (when limit is exceeded) are handled separately from execution errors via the `onReject` handler
- *
- * ## State Management and Selector
- *
- * The hook uses TanStack Store for reactive state management. You can subscribe to state changes
- * in two ways:
- *
- * **1. Using `rateLimiter.Subscribe` HOC (Recommended for component tree subscriptions)**
- *
- * Use the `Subscribe` HOC to subscribe to state changes deep in your component tree without
- * needing to pass a selector to the hook. This is ideal when you want to subscribe to state
- * in child components.
- *
- * **2. Using the `selector` parameter (For hook-level subscriptions)**
- *
- * The `selector` parameter allows you to specify which state changes will trigger a re-render
- * at the hook level, optimizing performance by preventing unnecessary re-renders when irrelevant
- * state changes occur.
- *
- * **By default, there will be no reactive state subscriptions** and you must opt-in to state
- * tracking by providing a selector function or using the `Subscribe` HOC. This prevents unnecessary
- * re-renders and gives you full control over when your component updates.
- *
- * Available state properties:
- * - `errorCount`: Number of function executions that have resulted in errors
- * - `executionTimes`: Array of timestamps when executions occurred for rate limiting calculations
- * - `isExecuting`: Whether the rate-limited function is currently executing asynchronously
- * - `lastResult`: The result from the most recent successful function execution
- * - `rejectionCount`: Number of function executions that have been rejected due to rate limiting
- * - `settleCount`: Number of function executions that have completed (success or error)
- * - `successCount`: Number of function executions that have completed successfully
- *
- * ## Unmount behavior
- *
- * By default, the hook aborts any in-flight execution when the component unmounts.
- * Abort only cancels underlying operations (e.g. fetch) when the abort signal from `getAbortSignal()` is passed to them.
- * Use the `onUnmount` option to customize this.
- *
- * @example
- * ```tsx
- * // Default behavior - no reactive state subscriptions
- * const asyncRateLimiter = useAsyncRateLimiter(
- *   async (id: string) => {
- *     const data = await api.fetchData(id);
- *     return data; // Return value is preserved
- *   },
- *   { limit: 5, window: 1000 } // 5 calls per second
- * );
- *
- * // Subscribe to state changes deep in component tree using Subscribe HOC
- * <asyncRateLimiter.Subscribe selector={(state) => ({ rejectionCount: state.rejectionCount })}>
- *   {({ rejectionCount }) => (
- *     <div>Rejections: {rejectionCount}</div>
- *   )}
- * </asyncRateLimiter.Subscribe>
- *
- * // Opt-in to re-render when execution state changes at hook level (optimized for loading indicators)
- * const asyncRateLimiter = useAsyncRateLimiter(
- *   async (id: string) => {
- *     const data = await api.fetchData(id);
- *     return data;
- *   },
- *   { limit: 5, window: 1000 },
- *   (state) => ({ isExecuting: state.isExecuting })
- * );
- *
- * // Opt-in to re-render when results are available (optimized for data display)
- * const asyncRateLimiter = useAsyncRateLimiter(
- *   async (id: string) => {
- *     const data = await api.fetchData(id);
- *     return data;
- *   },
- *   { limit: 5, window: 1000 },
- *   (state) => ({
- *     lastResult: state.lastResult,
- *     successCount: state.successCount
- *   })
- * );
- *
- * // Opt-in to re-render when error/rejection state changes (optimized for error handling)
- * const asyncRateLimiter = useAsyncRateLimiter(
- *   async (id: string) => {
- *     const data = await api.fetchData(id);
- *     return data;
- *   },
- *   {
- *     limit: 5,
- *     window: 1000,
- *     onError: (error) => console.error('API call failed:', error),
- *     onReject: (rateLimiter) => console.log('Rate limit exceeded')
- *   },
- *   (state) => ({
- *     errorCount: state.errorCount,
- *     rejectionCount: state.rejectionCount
- *   })
- * );
- *
- * // Opt-in to re-render when execution metrics change (optimized for stats display)
- * const asyncRateLimiter = useAsyncRateLimiter(
- *   async (id: string) => {
- *     const data = await api.fetchData(id);
- *     return data;
- *   },
- *   { limit: 5, window: 1000 },
- *   (state) => ({
- *     successCount: state.successCount,
- *     errorCount: state.errorCount,
- *     settleCount: state.settleCount,
- *     rejectionCount: state.rejectionCount
- *   })
- * );
- *
- * // Opt-in to re-render when execution times change (optimized for window calculations)
- * const asyncRateLimiter = useAsyncRateLimiter(
- *   async (id: string) => {
- *     const data = await api.fetchData(id);
- *     return data;
- *   },
- *   { limit: 5, window: 1000 },
- *   (state) => ({ executionTimes: state.executionTimes })
- * );
- *
- * // With state management and return value
- * const [data, setData] = useState(null);
- * const { maybeExecute, state } = useAsyncRateLimiter(
- *   async (query) => {
- *     const result = await searchAPI(query);
- *     setData(result);
- *     return result; // Return value can be used by the caller
- *   },
- *   {
- *     limit: 10,
- *     window: 60000, // 10 calls per minute
- *     onReject: (rateLimiter) => {
- *       console.log(`Rate limit exceeded. Try again in ${rateLimiter.getMsUntilNextWindow()}ms`);
- *     },
- *     onError: (error) => {
- *       console.error('API call failed:', error);
- *     }
- *   }
- * );
- *
- * // Access the selected state (will be empty object {} unless selector provided)
- * const { isExecuting, lastResult, rejectionCount } = state;
- * ```
- */
-export function useAsyncRateLimiter<
-  TFn extends AnyAsyncFunction,
-  TSelected = {},
->(
-  fn: TFn,
-  options: PreactAsyncRateLimiterOptions<TFn, TSelected>,
-  selector: (state: AsyncRateLimiterState<TFn>) => TSelected = () =>
-    ({}) as TSelected,
-): PreactAsyncRateLimiter<TFn, TSelected> {
-  const mergedOptions = {
-    ...useDefaultPacerOptions().asyncRateLimiter,
-    ...options,
-  } as PreactAsyncRateLimiterOptions<TFn, TSelected>
-
-  const [asyncRateLimiter] = useState(() => {
-    const rateLimiterInstance = new AsyncRateLimiter<TFn>(
-      fn,
-      mergedOptions,
-    ) as unknown as PreactAsyncRateLimiter<TFn, TSelected>
-
-    rateLimiterInstance.Subscribe = function Subscribe<TSelected>(props: {
-      selector: (state: AsyncRateLimiterState<TFn>) => TSelected
-      children: ((state: TSelected) => ComponentChildren) | ComponentChildren
-    }) {
-      const selected = useSelector(rateLimiterInstance.store, props.selector, {
-        compare: shallow,
-      })
-
-      return typeof props.children === 'function'
-        ? props.children(selected)
-        : props.children
-    }
-
-    return rateLimiterInstance
-  })
-
-  asyncRateLimiter.fn = fn
-  asyncRateLimiter.setOptions(mergedOptions)
-
-  /* eslint-disable react-hooks/exhaustive-deps -- cleanup only; runs on unmount */
-  useEffect(() => {
-    return () => {
-      if (mergedOptions.onUnmount) {
-        mergedOptions.onUnmount(asyncRateLimiter)
-      } else {
-        asyncRateLimiter.abort()
-      }
-    }
-  }, [])
-  /* eslint-enable react-hooks/exhaustive-deps */
-
-  const state = useSelector(asyncRateLimiter.store, selector, {
-    compare: shallow,
-  })
-
-  return useMemo(
-    () =>
-      ({
-        ...asyncRateLimiter,
-        state,
-      }) as PreactAsyncRateLimiter<TFn, TSelected>, // omit `store` in favor of `state`
-    [asyncRateLimiter, state],
-  )
-}

package/src/async-retryer/index.ts

@@ -1,2 +0,0 @@
-// re-export everything from the core pacer package, BUT ONLY from the async-retryer module
-export * from '@tanstack/pacer/async-retryer'

package/src/async-throttler/index.ts

@@ -1,5 +0,0 @@
-// re-export everything from the core pacer package, BUT ONLY from the async-throttler module
-export * from '@tanstack/pacer/async-throttler'
-
-export * from './useAsyncThrottler'
-export * from './useAsyncThrottledCallback'

package/src/async-throttler/useAsyncThrottledCallback.ts

@@ -1,52 +0,0 @@
-import { useCallback } from 'preact/hooks'
-import { useAsyncThrottler } from './useAsyncThrottler'
-import type { PreactAsyncThrottlerOptions } from './useAsyncThrottler'
-import type { AnyAsyncFunction } from '@tanstack/pacer/types'
-
-/**
- * A Preact hook that creates a throttled version of an async callback function.
- * This hook is a convenient wrapper around the `useAsyncThrottler` hook,
- * providing a stable, throttled async function reference for use in Preact components.
- *
- * The throttled async function will execute at most once within the specified wait time period,
- * regardless of how many times it is called. If called multiple times during the wait period,
- * only the first invocation will execute, and subsequent calls will be ignored until
- * the wait period has elapsed. The returned function always returns a promise
- * that resolves or rejects with the result of the original async function.
- *
- * This hook provides a simpler API compared to `useAsyncThrottler`, making it ideal for basic
- * async throttling needs. However, it does not expose the underlying AsyncThrottler instance.
- *
- * For advanced usage requiring features like:
- * - Manual cancellation
- * - Access to execution/error state
- * - Custom useCallback dependencies
- *
- * Consider using the `useAsyncThrottler` hook instead.
- *
- *
- * @example
- * ```tsx
- * // Throttle an async API call
- * const handleApiCall = useAsyncThrottledCallback(async (data) => {
- *   const result = await sendDataToServer(data);
- *   return result;
- * }, {
- *   wait: 200 // Execute at most once every 200ms
- * });
- *
- * // Use in an event handler
- * <button onClick={() => handleApiCall(formData)}>Send</button>
- * ```
- */
-export function useAsyncThrottledCallback<TFn extends AnyAsyncFunction>(
-  fn: TFn,
-  options: PreactAsyncThrottlerOptions<TFn, {}>,
-): (...args: Parameters<TFn>) => Promise<ReturnType<TFn>> {
-  const asyncThrottledFn = useAsyncThrottler(fn, options).maybeExecute
-  return useCallback(
-    (...args: Parameters<TFn>) =>
-      asyncThrottledFn(...args) as Promise<ReturnType<TFn>>,
-    [asyncThrottledFn],
-  )
-}

package/src/async-throttler/useAsyncThrottler.ts

@@ -1,285 +0,0 @@
-import { useEffect, useMemo, useState } from 'preact/hooks'
-import { AsyncThrottler } from '@tanstack/pacer/async-throttler'
-import { shallow, useSelector } from '@tanstack/preact-store'
-import { useDefaultPacerOptions } from '../provider/PacerProvider'
-import type { Store } from '@tanstack/preact-store'
-import type { AnyAsyncFunction } from '@tanstack/pacer/types'
-import type {
-  AsyncThrottlerOptions,
-  AsyncThrottlerState,
-} from '@tanstack/pacer/async-throttler'
-import type { ComponentChildren } from 'preact'
-
-export interface PreactAsyncThrottlerOptions<
-  TFn extends AnyAsyncFunction,
-  TSelected = {},
-> extends AsyncThrottlerOptions<TFn> {
-  /**
-   * Optional callback invoked when the component unmounts. Receives the throttler instance.
-   * When provided, replaces the default cleanup (cancel + abort); use it to call flush(), reset(), cancel(), add logging, etc.
-   */
-  onUnmount?: (throttler: PreactAsyncThrottler<TFn, TSelected>) => void
-}
-
-export interface PreactAsyncThrottler<
-  TFn extends AnyAsyncFunction,
-  TSelected = {},
-> extends Omit<AsyncThrottler<TFn>, 'store'> {
-  /**
-   * A Preact HOC (Higher Order Component) that allows you to subscribe to the async throttler state.
-   *
-   * This is useful for opting into state re-renders for specific parts of the throttler state
-   * deep in your component tree without needing to pass a selector to the hook.
-   *
-   * @example
-   * <throttler.Subscribe selector={(state) => ({ isPending: state.isPending })}>
-   *   {({ isPending }) => (
-   *     <div>{isPending ? 'Loading...' : 'Ready'}</div>
-   *   )}
-   * </throttler.Subscribe>
-   */
-  Subscribe: <TSelected>(props: {
-    selector: (state: AsyncThrottlerState<TFn>) => TSelected
-    children: ((state: TSelected) => ComponentChildren) | ComponentChildren
-  }) => ComponentChildren
-  /**
-   * Reactive state that will be updated and re-rendered when the throttler state changes
-   *
-   * Use this instead of `throttler.store.state`
-   */
-  readonly state: Readonly<TSelected>
-  /**
-   * @deprecated Use `throttler.state` instead of `throttler.store.state` if you want to read reactive state.
-   * The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.
-   * Although, you can make the state reactive by using the `useSelector` in your own usage.
-   */
-  readonly store: Store<Readonly<AsyncThrottlerState<TFn>>>
-}
-
-/**
- * A low-level Preact hook that creates an `AsyncThrottler` instance to limit how often an async function can execute.
- *
- * This hook is designed to be flexible and state-management agnostic - it simply returns a throttler instance that
- * you can integrate with any state management solution (useState, Redux, Zustand, Jotai, etc).
- *
- * Async throttling ensures an async function executes at most once within a specified time window,
- * regardless of how many times it is called. This is useful for rate-limiting expensive API calls,
- * database operations, or other async tasks.
- *
- * Unlike the non-async Throttler, this async version supports returning values from the throttled function,
- * making it ideal for API calls and other async operations where you want the result of the `maybeExecute` call
- * instead of setting the result on a state variable from within the throttled function.
- *
- * Error Handling:
- * - If an `onError` handler is provided, it will be called with the error and throttler instance
- * - If `throwOnError` is true (default when no onError handler is provided), the error will be thrown
- * - If `throwOnError` is false (default when onError handler is provided), the error will be swallowed
- * - Both onError and throwOnError can be used together - the handler will be called before any error is thrown
- * - The error state can be checked using the underlying AsyncThrottler instance
- *
- * ## State Management and Selector
- *
- * The hook uses TanStack Store for reactive state management. You can subscribe to state changes
- * in two ways:
- *
- * **1. Using `throttler.Subscribe` HOC (Recommended for component tree subscriptions)**
- *
- * Use the `Subscribe` HOC to subscribe to state changes deep in your component tree without
- * needing to pass a selector to the hook. This is ideal when you want to subscribe to state
- * in child components.
- *
- * **2. Using the `selector` parameter (For hook-level subscriptions)**
- *
- * The `selector` parameter allows you to specify which state changes will trigger a re-render
- * at the hook level, optimizing performance by preventing unnecessary re-renders when irrelevant
- * state changes occur.
- *
- * **By default, there will be no reactive state subscriptions** and you must opt-in to state
- * tracking by providing a selector function or using the `Subscribe` HOC. This prevents unnecessary
- * re-renders and gives you full control over when your component updates.
- *
- * Available state properties:
- * - `errorCount`: Number of function executions that have resulted in errors
- * - `isExecuting`: Whether the throttled function is currently executing asynchronously
- * - `isPending`: Whether the throttler is waiting for the timeout to trigger execution
- * - `lastArgs`: The arguments from the most recent call to maybeExecute
- * - `lastExecutionTime`: Timestamp of the last function execution in milliseconds
- * - `lastResult`: The result from the most recent successful function execution
- * - `nextExecutionTime`: Timestamp when the next execution can occur in milliseconds
- * - `settleCount`: Number of function executions that have completed (success or error)
- * - `status`: Current execution status ('disabled' | 'idle' | 'pending' | 'executing' | 'settled')
- * - `successCount`: Number of function executions that have completed successfully
- *
- * ## Unmount behavior
- *
- * By default, the hook cancels any pending execution and aborts any in-flight execution when the component unmounts.
- * Abort only cancels underlying operations (e.g. fetch) when the abort signal from `getAbortSignal()` is passed to them.
- * Use the `onUnmount` option to customize this. For example, to flush pending work instead:
- *
- * ```tsx
- * const throttler = useAsyncThrottler(fn, {
- *   wait: 1000,
- *   onUnmount: (t) => t.flush()
- * });
- * ```
- *
- * Note: For async utils, `flush()` returns a Promise and runs fire-and-forget in the cleanup.
- * If your throttled function updates Preact state, those updates may run after the component has
- * unmounted, which can cause "setState on unmounted component" warnings. Guard your callbacks
- * accordingly when using onUnmount with flush.
- *
- * @example
- * ```tsx
- * // Default behavior - no reactive state subscriptions
- * const asyncThrottler = useAsyncThrottler(
- *   async (id: string) => {
- *     const data = await api.fetchData(id);
- *     return data; // Return value is preserved
- *   },
- *   { wait: 1000 }
- * );
- *
- * // Subscribe to state changes deep in component tree using Subscribe HOC
- * <asyncThrottler.Subscribe selector={(state) => ({ isPending: state.isPending })}>
- *   {({ isPending }) => (
- *     <div>{isPending ? 'Processing...' : 'Ready'}</div>
- *   )}
- * </asyncThrottler.Subscribe>
- *
- * // Opt-in to re-render when execution state changes at hook level (optimized for loading indicators)
- * const asyncThrottler = useAsyncThrottler(
- *   async (id: string) => {
- *     const data = await api.fetchData(id);
- *     return data;
- *   },
- *   { wait: 1000 },
- *   (state) => ({
- *     isExecuting: state.isExecuting,
- *     isPending: state.isPending,
- *     status: state.status
- *   })
- * );
- *
- * // Opt-in to re-render when results are available (optimized for data display)
- * const asyncThrottler = useAsyncThrottler(
- *   async (id: string) => {
- *     const data = await api.fetchData(id);
- *     return data;
- *   },
- *   { wait: 1000 },
- *   (state) => ({
- *     lastResult: state.lastResult,
- *     successCount: state.successCount,
- *     settleCount: state.settleCount
- *   })
- * );
- *
- * // Opt-in to re-render when error state changes (optimized for error handling)
- * const asyncThrottler = useAsyncThrottler(
- *   async (id: string) => {
- *     const data = await api.fetchData(id);
- *     return data;
- *   },
- *   {
- *     wait: 1000,
- *     onError: (error) => console.error('API call failed:', error)
- *   },
- *   (state) => ({
- *     errorCount: state.errorCount,
- *     status: state.status
- *   })
- * );
- *
- * // Opt-in to re-render when timing information changes (optimized for timing displays)
- * const asyncThrottler = useAsyncThrottler(
- *   async (id: string) => {
- *     const data = await api.fetchData(id);
- *     return data;
- *   },
- *   { wait: 1000 },
- *   (state) => ({
- *     lastExecutionTime: state.lastExecutionTime,
- *     nextExecutionTime: state.nextExecutionTime
- *   })
- * );
- *
- * // With state management and return value
- * const [data, setData] = useState(null);
- * const { maybeExecute, state } = useAsyncThrottler(
- *   async (query) => {
- *     const result = await searchAPI(query);
- *     setData(result);
- *     return result; // Return value can be used by the caller
- *   },
- *   {
- *     wait: 2000,
- *     leading: true,   // Execute immediately on first call
- *     trailing: false  // Skip trailing edge updates
- *   }
- * );
- *
- * // Access the selected state (will be empty object {} unless selector provided)
- * const { isExecuting, lastResult } = state;
- * ```
- */
-export function useAsyncThrottler<TFn extends AnyAsyncFunction, TSelected = {}>(
-  fn: TFn,
-  options: PreactAsyncThrottlerOptions<TFn, TSelected>,
-  selector: (state: AsyncThrottlerState<TFn>) => TSelected = () =>
-    ({}) as TSelected,
-): PreactAsyncThrottler<TFn, TSelected> {
-  const mergedOptions = {
-    ...useDefaultPacerOptions().asyncThrottler,
-    ...options,
-  } as PreactAsyncThrottlerOptions<TFn, TSelected>
-  const [asyncThrottler] = useState(() => {
-    const throttlerInstance = new AsyncThrottler<TFn>(
-      fn,
-      mergedOptions,
-    ) as unknown as PreactAsyncThrottler<TFn, TSelected>
-
-    throttlerInstance.Subscribe = function Subscribe<TSelected>(props: {
-      selector: (state: AsyncThrottlerState<TFn>) => TSelected
-      children: ((state: TSelected) => ComponentChildren) | ComponentChildren
-    }) {
-      const selected = useSelector(throttlerInstance.store, props.selector, {
-        compare: shallow,
-      })
-
-      return typeof props.children === 'function'
-        ? props.children(selected)
-        : props.children
-    }
-
-    return throttlerInstance
-  })
-
-  asyncThrottler.fn = fn
-  asyncThrottler.setOptions(mergedOptions)
-
-  const state = useSelector(asyncThrottler.store, selector, {
-    compare: shallow,
-  })
-
-  /* eslint-disable react-hooks/exhaustive-deps -- cleanup only; runs on unmount */
-  useEffect(() => {
-    return () => {
-      if (mergedOptions.onUnmount) {
-        mergedOptions.onUnmount(asyncThrottler)
-      } else {
-        asyncThrottler.cancel()
-        asyncThrottler.abort()
-      }
-    }
-  }, [])
-  /* eslint-enable react-hooks/exhaustive-deps */
-
-  return useMemo(
-    () =>
-      ({
-        ...asyncThrottler,
-        state,
-      }) as PreactAsyncThrottler<TFn, TSelected>, // omit `store` in favor of `state`
-    [asyncThrottler, state],
-  )
-}

package/src/batcher/index.ts

@@ -1,4 +0,0 @@
-export * from '@tanstack/pacer/batcher'
-
-export * from './useBatcher'
-export * from './useBatchedCallback'

package/src/batcher/useBatchedCallback.ts

@@ -1,46 +0,0 @@
-import { useCallback } from 'preact/hooks'
-import { useBatcher } from './useBatcher'
-import type { PreactBatcherOptions } from './useBatcher'
-
-/**
- * A Preact hook that creates a batched version of a callback function.
- * This hook is essentially a wrapper around the basic `batch` function
- * that is exported from `@tanstack/pacer`,
- * but optimized for Preact with reactive options and a stable function reference.
- *
- * The batched function will collect individual calls into batches and execute them
- * when batch conditions are met (max size reached, wait time elapsed, or custom logic).
- *
- * This hook provides a simpler API compared to `useBatcher`, making it ideal for basic
- * batching needs. However, it does not expose the underlying Batcher instance.
- *
- * For advanced usage requiring features like:
- * - Manual batch execution
- * - Access to batch state and metrics
- * - Custom useCallback dependencies
- *
- * Consider using the `useBatcher` hook instead.
- *
- * @example
- * ```tsx
- * // Batch analytics events
- * const trackEvents = useBatchedCallback((events: AnalyticsEvent[]) => {
- *   sendAnalytics(events);
- * }, {
- *   maxSize: 5,    // Process when 5 events collected
- *   wait: 2000     // Or after 2 seconds
- * });
- *
- * // Use in event handlers
- * <button onClick={() => trackEvents({ type: 'click', target: 'button' })}>
- *   Click me
- * </button>
- * ```
- */
-export function useBatchedCallback<TValue>(
-  fn: (items: Array<TValue>) => void,
-  options: PreactBatcherOptions<TValue, {}>,
-): (item: TValue) => void {
-  const batchedFn = useBatcher(fn, options).addItem
-  return useCallback((item: TValue) => batchedFn(item), [batchedFn])
-}