@tanstack/solid-pacer 0.22.0 → 0.23.0

package/dist/async-batcher/createAsyncBatcher.cjs

@@ -1,166 +0,0 @@
-const require_PacerProvider = require('../provider/PacerProvider.cjs');
-let solid_js = require("solid-js");
-let _tanstack_pacer_async_batcher = require("@tanstack/pacer/async-batcher");
-let _tanstack_solid_store = require("@tanstack/solid-store");
-
-//#region src/async-batcher/createAsyncBatcher.ts
-/**
-* Creates a Solid-compatible AsyncBatcher instance for managing asynchronous batches of items, exposing Solid signals for all stateful properties.
-*
-* This is the async version of the createBatcher hook. Unlike the sync version, this async batcher:
-* - Handles promises and returns results from batch executions
-* - Provides error handling with configurable error behavior
-* - Tracks success, error, and settle counts separately
-* - Has state tracking for when batches are executing
-* - Returns the result of the batch function execution
-*
-* Features:
-* - Configurable batch size and wait time
-* - Custom batch processing logic via getShouldExecute
-* - Event callbacks for monitoring batch operations
-* - Error handling for failed batch operations
-* - Automatic or manual batch processing
-* - All stateful properties (items, counts, etc.) are exposed as Solid signals for reactivity
-*
-* The batcher collects items and processes them in batches based on:
-* - Maximum batch size (number of items per batch)
-* - Time-based batching (process after X milliseconds)
-* - Custom batch processing logic via getShouldExecute
-*
-* Error Handling:
-* - If an `onError` handler is provided, it will be called with the error and batcher 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 AsyncBatcher 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 `batcher.Subscribe` component (Recommended for component tree subscriptions)**
-*
-* Use the `Subscribe` component 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 reactive updates
-* at the hook level, optimizing performance by preventing unnecessary updates 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` component. This prevents unnecessary
-* updates and gives you full control over when your component tracks state changes.
-*
-* Available state properties:
-* - `errorCount`: Number of failed batch executions
-* - `executionCount`: Total number of batch execution attempts (successful + failed)
-* - `hasError`: Whether the last batch execution resulted in an error
-* - `isExecuting`: Whether a batch execution is currently in progress
-* - `items`: Array of items currently queued for batching
-* - `lastError`: The error from the most recent failed batch execution (if any)
-* - `lastResult`: The result from the most recent successful batch execution
-* - `settleCount`: Number of batch executions that have completed (successful or failed)
-* - `successCount`: Number of successful batch executions
-*
-* ## Unmount behavior
-*
-* By default, the primitive cancels any pending batch and aborts any in-flight execution when the owning 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 batcher = createAsyncBatcher(fn, {
-*   maxSize: 10,
-*   wait: 2000,
-*   onUnmount: (b) => b.flush()
-* });
-* ```
-*
-* Note: For async utils, `flush()` returns a Promise and runs fire-and-forget in the cleanup.
-* If your batch function updates Solid signals, those updates may run after the component has
-* unmounted, which can cause unexpected reactive updates. Guard your callbacks accordingly when
-* using onUnmount with flush.
-*
-* Example usage:
-* ```tsx
-* // Default behavior - no reactive state subscriptions
-* const asyncBatcher = createAsyncBatcher(
-*   async (items) => {
-*     const results = await Promise.all(items.map(item => processItem(item)));
-*     return results;
-*   },
-*   {
-*     maxSize: 10,
-*     wait: 2000,
-*     onSuccess: (result) => {
-*       console.log('Batch processed successfully:', result);
-*     },
-*     onError: (error) => {
-*       console.error('Batch processing failed:', error);
-*     }
-*   }
-* );
-*
-* // Opt-in to track items or isExecuting changes (optimized for UI updates)
-* const asyncBatcher = createAsyncBatcher(
-*   async (items) => {
-*     const results = await Promise.all(items.map(item => processItem(item)));
-*     return results;
-*   },
-*   { maxSize: 10, wait: 2000 },
-*   (state) => ({ items: state.items, isExecuting: state.isExecuting })
-* );
-*
-* // Opt-in to track error state changes (optimized for error handling)
-* const asyncBatcher = createAsyncBatcher(
-*   async (items) => {
-*     const results = await Promise.all(items.map(item => processItem(item)));
-*     return results;
-*   },
-*   { maxSize: 10, wait: 2000 },
-*   (state) => ({ hasError: state.hasError, lastError: state.lastError })
-* );
-*
-* // Add items to batch
-* asyncBatcher.addItem(newItem);
-*
-* // Manually execute batch
-* const result = await asyncBatcher.execute();
-*
-* // Access the selected state (will be empty object {} unless selector provided)
-* const { items, isExecuting } = asyncBatcher.state();
-* ```
-*/
-function createAsyncBatcher(fn, options = {}, selector = () => ({})) {
-	const mergedOptions = {
-		...require_PacerProvider.useDefaultPacerOptions().asyncBatcher,
-		...options
-	};
-	const asyncBatcher = new _tanstack_pacer_async_batcher.AsyncBatcher(fn, mergedOptions);
-	asyncBatcher.Subscribe = function Subscribe(props) {
-		const selected = (0, _tanstack_solid_store.useSelector)(asyncBatcher.store, props.selector, { compare: _tanstack_solid_store.shallow });
-		return typeof props.children === "function" ? props.children(selected) : props.children;
-	};
-	const state = (0, _tanstack_solid_store.useSelector)(asyncBatcher.store, selector, { compare: _tanstack_solid_store.shallow });
-	(0, solid_js.createEffect)(() => {
-		(0, solid_js.onCleanup)(() => {
-			if (mergedOptions.onUnmount) mergedOptions.onUnmount(asyncBatcher);
-			else {
-				asyncBatcher.cancel();
-				asyncBatcher.abort();
-			}
-		});
-	});
-	return {
-		...asyncBatcher,
-		state
-	};
-}
-
-//#endregion
-exports.createAsyncBatcher = createAsyncBatcher;
-//# sourceMappingURL=createAsyncBatcher.cjs.map

package/dist/async-batcher/createAsyncBatcher.cjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"createAsyncBatcher.cjs","names":["useDefaultPacerOptions","AsyncBatcher","useSelector","shallow"],"sources":["../../src/async-batcher/createAsyncBatcher.ts"],"sourcesContent":["import { AsyncBatcher } from '@tanstack/pacer/async-batcher'\nimport { shallow, useSelector } from '@tanstack/solid-store'\nimport { createEffect, onCleanup } from 'solid-js'\nimport { useDefaultPacerOptions } from '../provider/PacerProvider'\nimport type { Store } from '@tanstack/solid-store'\nimport type { Accessor, JSX } from 'solid-js'\nimport type {\n  AsyncBatcherOptions,\n  AsyncBatcherState,\n} from '@tanstack/pacer/async-batcher'\n\nexport interface SolidAsyncBatcherOptions<\n  TValue,\n  TSelected = {},\n> extends AsyncBatcherOptions<TValue> {\n  /**\n   * Optional callback invoked when the owning component unmounts. Receives the batcher instance.\n   * When provided, replaces the default cleanup (cancel + abort); use it to call flush(), reset(), cancel(), add logging, etc.\n   */\n  onUnmount?: (batcher: SolidAsyncBatcher<TValue, TSelected>) => void\n}\n\nexport interface SolidAsyncBatcher<TValue, TSelected = {}> extends Omit<\n  AsyncBatcher<TValue>,\n  'store'\n> {\n  /**\n   * A Solid component that allows you to subscribe to the batcher state.\n   *\n   * This is useful for tracking specific parts of the batcher state\n   * deep in your component tree without needing to pass a selector to the hook.\n   *\n   * @example\n   * <batcher.Subscribe selector={(state) => ({ size: state.size, isExecuting: state.isExecuting })}>\n   *   {(state) => (\n   *     <div>Batch: {state().size} items, {state().isExecuting ? 'Executing...' : 'Idle'}</div>\n   *   )}\n   * </batcher.Subscribe>\n   */\n  Subscribe: <TSelected>(props: {\n    selector: (state: AsyncBatcherState<TValue>) => TSelected\n    children: ((state: Accessor<TSelected>) => JSX.Element) | JSX.Element\n  }) => JSX.Element\n  /**\n   * Reactive state that will be updated when the batcher state changes\n   *\n   * Use this instead of `batcher.store.state`\n   */\n  readonly state: Accessor<Readonly<TSelected>>\n  /**\n   * @deprecated Use `batcher.state` instead of `batcher.store.state` if you want to read reactive state.\n   * The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.\n   * Although, you can make the state reactive by using the `useSelector` in your own usage.\n   */\n  readonly store: Store<Readonly<AsyncBatcherState<TValue>>>\n}\n\n/**\n * Creates a Solid-compatible AsyncBatcher instance for managing asynchronous batches of items, exposing Solid signals for all stateful properties.\n *\n * This is the async version of the createBatcher hook. Unlike the sync version, this async batcher:\n * - Handles promises and returns results from batch executions\n * - Provides error handling with configurable error behavior\n * - Tracks success, error, and settle counts separately\n * - Has state tracking for when batches are executing\n * - Returns the result of the batch function execution\n *\n * Features:\n * - Configurable batch size and wait time\n * - Custom batch processing logic via getShouldExecute\n * - Event callbacks for monitoring batch operations\n * - Error handling for failed batch operations\n * - Automatic or manual batch processing\n * - All stateful properties (items, counts, etc.) are exposed as Solid signals for reactivity\n *\n * The batcher collects items and processes them in batches based on:\n * - Maximum batch size (number of items per batch)\n * - Time-based batching (process after X milliseconds)\n * - Custom batch processing logic via getShouldExecute\n *\n * Error Handling:\n * - If an `onError` handler is provided, it will be called with the error and batcher instance\n * - If `throwOnError` is true (default when no onError handler is provided), the error will be thrown\n * - If `throwOnError` is false (default when onError handler is provided), the error will be swallowed\n * - Both onError and throwOnError can be used together; the handler will be called before any error is thrown\n * - The error state can be checked using the underlying AsyncBatcher instance\n *\n * ## State Management and Selector\n *\n * The hook uses TanStack Store for reactive state management. You can subscribe to state changes\n * in two ways:\n *\n * **1. Using `batcher.Subscribe` component (Recommended for component tree subscriptions)**\n *\n * Use the `Subscribe` component to subscribe to state changes deep in your component tree without\n * needing to pass a selector to the hook. This is ideal when you want to subscribe to state\n * in child components.\n *\n * **2. Using the `selector` parameter (For hook-level subscriptions)**\n *\n * The `selector` parameter allows you to specify which state changes will trigger reactive updates\n * at the hook level, optimizing performance by preventing unnecessary updates when irrelevant\n * state changes occur.\n *\n * **By default, there will be no reactive state subscriptions** and you must opt-in to state\n * tracking by providing a selector function or using the `Subscribe` component. This prevents unnecessary\n * updates and gives you full control over when your component tracks state changes.\n *\n * Available state properties:\n * - `errorCount`: Number of failed batch executions\n * - `executionCount`: Total number of batch execution attempts (successful + failed)\n * - `hasError`: Whether the last batch execution resulted in an error\n * - `isExecuting`: Whether a batch execution is currently in progress\n * - `items`: Array of items currently queued for batching\n * - `lastError`: The error from the most recent failed batch execution (if any)\n * - `lastResult`: The result from the most recent successful batch execution\n * - `settleCount`: Number of batch executions that have completed (successful or failed)\n * - `successCount`: Number of successful batch executions\n *\n * ## Unmount behavior\n *\n * By default, the primitive cancels any pending batch and aborts any in-flight execution when the owning component unmounts.\n * Abort only cancels underlying operations (e.g. fetch) when the abort signal from `getAbortSignal()` is passed to them.\n * Use the `onUnmount` option to customize this. For example, to flush pending work instead:\n *\n * ```tsx\n * const batcher = createAsyncBatcher(fn, {\n *   maxSize: 10,\n *   wait: 2000,\n *   onUnmount: (b) => b.flush()\n * });\n * ```\n *\n * Note: For async utils, `flush()` returns a Promise and runs fire-and-forget in the cleanup.\n * If your batch function updates Solid signals, those updates may run after the component has\n * unmounted, which can cause unexpected reactive updates. Guard your callbacks accordingly when\n * using onUnmount with flush.\n *\n * Example usage:\n * ```tsx\n * // Default behavior - no reactive state subscriptions\n * const asyncBatcher = createAsyncBatcher(\n *   async (items) => {\n *     const results = await Promise.all(items.map(item => processItem(item)));\n *     return results;\n *   },\n *   {\n *     maxSize: 10,\n *     wait: 2000,\n *     onSuccess: (result) => {\n *       console.log('Batch processed successfully:', result);\n *     },\n *     onError: (error) => {\n *       console.error('Batch processing failed:', error);\n *     }\n *   }\n * );\n *\n * // Opt-in to track items or isExecuting changes (optimized for UI updates)\n * const asyncBatcher = createAsyncBatcher(\n *   async (items) => {\n *     const results = await Promise.all(items.map(item => processItem(item)));\n *     return results;\n *   },\n *   { maxSize: 10, wait: 2000 },\n *   (state) => ({ items: state.items, isExecuting: state.isExecuting })\n * );\n *\n * // Opt-in to track error state changes (optimized for error handling)\n * const asyncBatcher = createAsyncBatcher(\n *   async (items) => {\n *     const results = await Promise.all(items.map(item => processItem(item)));\n *     return results;\n *   },\n *   { maxSize: 10, wait: 2000 },\n *   (state) => ({ hasError: state.hasError, lastError: state.lastError })\n * );\n *\n * // Add items to batch\n * asyncBatcher.addItem(newItem);\n *\n * // Manually execute batch\n * const result = await asyncBatcher.execute();\n *\n * // Access the selected state (will be empty object {} unless selector provided)\n * const { items, isExecuting } = asyncBatcher.state();\n * ```\n */\nexport function createAsyncBatcher<TValue, TSelected = {}>(\n  fn: (items: Array<TValue>) => Promise<any>,\n  options: SolidAsyncBatcherOptions<TValue, TSelected> = {},\n  selector: (state: AsyncBatcherState<TValue>) => TSelected = () =>\n    ({}) as TSelected,\n): SolidAsyncBatcher<TValue, TSelected> {\n  const mergedOptions = {\n    ...useDefaultPacerOptions().asyncBatcher,\n    ...options,\n  } as SolidAsyncBatcherOptions<TValue, TSelected>\n  const asyncBatcher = new AsyncBatcher<TValue>(\n    fn,\n    mergedOptions,\n  ) as unknown as SolidAsyncBatcher<TValue, TSelected>\n\n  asyncBatcher.Subscribe = function Subscribe<TSelected>(props: {\n    selector: (state: AsyncBatcherState<TValue>) => TSelected\n    children: ((state: Accessor<TSelected>) => JSX.Element) | JSX.Element\n  }) {\n    const selected = useSelector(asyncBatcher.store, props.selector, {\n      compare: shallow,\n    })\n\n    return typeof props.children === 'function'\n      ? props.children(selected)\n      : props.children\n  }\n\n  const state = useSelector(asyncBatcher.store, selector, { compare: shallow })\n\n  createEffect(() => {\n    onCleanup(() => {\n      if (mergedOptions.onUnmount) {\n        mergedOptions.onUnmount(asyncBatcher)\n      } else {\n        asyncBatcher.cancel()\n        asyncBatcher.abort()\n      }\n    })\n  })\n\n  return {\n    ...asyncBatcher,\n    state,\n  } as SolidAsyncBatcher<TValue, TSelected> // omit `store` in favor of `state`\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA4LA,SAAgB,mBACd,IACA,UAAuD,CAAC,GACxD,kBACG,CAAC,IACkC;CACtC,MAAM,gBAAgB;EACpB,GAAGA,6CAAuB,CAAC,CAAC;EAC5B,GAAG;CACL;CACA,MAAM,eAAe,IAAIC,2CACvB,IACA,aACF;CAEA,aAAa,YAAY,SAAS,UAAqB,OAGpD;EACD,MAAM,eAAWC,mCAAY,aAAa,OAAO,MAAM,UAAU,EAC/D,SAASC,8BACX,CAAC;EAED,OAAO,OAAO,MAAM,aAAa,aAC7B,MAAM,SAAS,QAAQ,IACvB,MAAM;CACZ;CAEA,MAAM,YAAQD,mCAAY,aAAa,OAAO,UAAU,EAAE,SAASC,8BAAQ,CAAC;CAE5E,iCAAmB;EACjB,8BAAgB;GACd,IAAI,cAAc,WAChB,cAAc,UAAU,YAAY;QAC/B;IACL,aAAa,OAAO;IACpB,aAAa,MAAM;GACrB;EACF,CAAC;CACH,CAAC;CAED,OAAO;EACL,GAAG;EACH;CACF;AACF"}

package/dist/async-batcher/createAsyncBatcher.d.cts

@@ -1,177 +0,0 @@
-import { AsyncBatcher, AsyncBatcherOptions, AsyncBatcherState } from "@tanstack/pacer/async-batcher";
-import { Store } from "@tanstack/solid-store";
-import { Accessor, JSX } from "solid-js";
-//#region src/async-batcher/createAsyncBatcher.d.ts
-interface SolidAsyncBatcherOptions<TValue, TSelected = {}> extends AsyncBatcherOptions<TValue> {
-  /**
-   * Optional callback invoked when the owning component unmounts. Receives the batcher instance.
-   * When provided, replaces the default cleanup (cancel + abort); use it to call flush(), reset(), cancel(), add logging, etc.
-   */
-  onUnmount?: (batcher: SolidAsyncBatcher<TValue, TSelected>) => void;
-}
-interface SolidAsyncBatcher<TValue, TSelected = {}> extends Omit<AsyncBatcher<TValue>, 'store'> {
-  /**
-   * A Solid component that allows you to subscribe to the batcher state.
-   *
-   * This is useful for tracking specific parts of the batcher state
-   * deep in your component tree without needing to pass a selector to the hook.
-   *
-   * @example
-   * <batcher.Subscribe selector={(state) => ({ size: state.size, isExecuting: state.isExecuting })}>
-   *   {(state) => (
-   *     <div>Batch: {state().size} items, {state().isExecuting ? 'Executing...' : 'Idle'}</div>
-   *   )}
-   * </batcher.Subscribe>
-   */
-  Subscribe: <TSelected>(props: {
-    selector: (state: AsyncBatcherState<TValue>) => TSelected;
-    children: ((state: Accessor<TSelected>) => JSX.Element) | JSX.Element;
-  }) => JSX.Element;
-  /**
-   * Reactive state that will be updated when the batcher state changes
-   *
-   * Use this instead of `batcher.store.state`
-   */
-  readonly state: Accessor<Readonly<TSelected>>;
-  /**
-   * @deprecated Use `batcher.state` instead of `batcher.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<AsyncBatcherState<TValue>>>;
-}
-/**
- * Creates a Solid-compatible AsyncBatcher instance for managing asynchronous batches of items, exposing Solid signals for all stateful properties.
- *
- * This is the async version of the createBatcher hook. Unlike the sync version, this async batcher:
- * - Handles promises and returns results from batch executions
- * - Provides error handling with configurable error behavior
- * - Tracks success, error, and settle counts separately
- * - Has state tracking for when batches are executing
- * - Returns the result of the batch function execution
- *
- * Features:
- * - Configurable batch size and wait time
- * - Custom batch processing logic via getShouldExecute
- * - Event callbacks for monitoring batch operations
- * - Error handling for failed batch operations
- * - Automatic or manual batch processing
- * - All stateful properties (items, counts, etc.) are exposed as Solid signals for reactivity
- *
- * The batcher collects items and processes them in batches based on:
- * - Maximum batch size (number of items per batch)
- * - Time-based batching (process after X milliseconds)
- * - Custom batch processing logic via getShouldExecute
- *
- * Error Handling:
- * - If an `onError` handler is provided, it will be called with the error and batcher 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 AsyncBatcher 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 `batcher.Subscribe` component (Recommended for component tree subscriptions)**
- *
- * Use the `Subscribe` component 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 reactive updates
- * at the hook level, optimizing performance by preventing unnecessary updates 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` component. This prevents unnecessary
- * updates and gives you full control over when your component tracks state changes.
- *
- * Available state properties:
- * - `errorCount`: Number of failed batch executions
- * - `executionCount`: Total number of batch execution attempts (successful + failed)
- * - `hasError`: Whether the last batch execution resulted in an error
- * - `isExecuting`: Whether a batch execution is currently in progress
- * - `items`: Array of items currently queued for batching
- * - `lastError`: The error from the most recent failed batch execution (if any)
- * - `lastResult`: The result from the most recent successful batch execution
- * - `settleCount`: Number of batch executions that have completed (successful or failed)
- * - `successCount`: Number of successful batch executions
- *
- * ## Unmount behavior
- *
- * By default, the primitive cancels any pending batch and aborts any in-flight execution when the owning 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 batcher = createAsyncBatcher(fn, {
- *   maxSize: 10,
- *   wait: 2000,
- *   onUnmount: (b) => b.flush()
- * });
- * ```
- *
- * Note: For async utils, `flush()` returns a Promise and runs fire-and-forget in the cleanup.
- * If your batch function updates Solid signals, those updates may run after the component has
- * unmounted, which can cause unexpected reactive updates. Guard your callbacks accordingly when
- * using onUnmount with flush.
- *
- * Example usage:
- * ```tsx
- * // Default behavior - no reactive state subscriptions
- * const asyncBatcher = createAsyncBatcher(
- *   async (items) => {
- *     const results = await Promise.all(items.map(item => processItem(item)));
- *     return results;
- *   },
- *   {
- *     maxSize: 10,
- *     wait: 2000,
- *     onSuccess: (result) => {
- *       console.log('Batch processed successfully:', result);
- *     },
- *     onError: (error) => {
- *       console.error('Batch processing failed:', error);
- *     }
- *   }
- * );
- *
- * // Opt-in to track items or isExecuting changes (optimized for UI updates)
- * const asyncBatcher = createAsyncBatcher(
- *   async (items) => {
- *     const results = await Promise.all(items.map(item => processItem(item)));
- *     return results;
- *   },
- *   { maxSize: 10, wait: 2000 },
- *   (state) => ({ items: state.items, isExecuting: state.isExecuting })
- * );
- *
- * // Opt-in to track error state changes (optimized for error handling)
- * const asyncBatcher = createAsyncBatcher(
- *   async (items) => {
- *     const results = await Promise.all(items.map(item => processItem(item)));
- *     return results;
- *   },
- *   { maxSize: 10, wait: 2000 },
- *   (state) => ({ hasError: state.hasError, lastError: state.lastError })
- * );
- *
- * // Add items to batch
- * asyncBatcher.addItem(newItem);
- *
- * // Manually execute batch
- * const result = await asyncBatcher.execute();
- *
- * // Access the selected state (will be empty object {} unless selector provided)
- * const { items, isExecuting } = asyncBatcher.state();
- * ```
- */
-declare function createAsyncBatcher<TValue, TSelected = {}>(fn: (items: Array<TValue>) => Promise<any>, options?: SolidAsyncBatcherOptions<TValue, TSelected>, selector?: (state: AsyncBatcherState<TValue>) => TSelected): SolidAsyncBatcher<TValue, TSelected>;
-//#endregion
-export { SolidAsyncBatcher, SolidAsyncBatcherOptions, createAsyncBatcher };
-//# sourceMappingURL=createAsyncBatcher.d.cts.map

package/dist/async-batcher/createAsyncBatcher.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"createAsyncBatcher.js","names":[],"sources":["../../src/async-batcher/createAsyncBatcher.ts"],"sourcesContent":["import { AsyncBatcher } from '@tanstack/pacer/async-batcher'\nimport { shallow, useSelector } from '@tanstack/solid-store'\nimport { createEffect, onCleanup } from 'solid-js'\nimport { useDefaultPacerOptions } from '../provider/PacerProvider'\nimport type { Store } from '@tanstack/solid-store'\nimport type { Accessor, JSX } from 'solid-js'\nimport type {\n  AsyncBatcherOptions,\n  AsyncBatcherState,\n} from '@tanstack/pacer/async-batcher'\n\nexport interface SolidAsyncBatcherOptions<\n  TValue,\n  TSelected = {},\n> extends AsyncBatcherOptions<TValue> {\n  /**\n   * Optional callback invoked when the owning component unmounts. Receives the batcher instance.\n   * When provided, replaces the default cleanup (cancel + abort); use it to call flush(), reset(), cancel(), add logging, etc.\n   */\n  onUnmount?: (batcher: SolidAsyncBatcher<TValue, TSelected>) => void\n}\n\nexport interface SolidAsyncBatcher<TValue, TSelected = {}> extends Omit<\n  AsyncBatcher<TValue>,\n  'store'\n> {\n  /**\n   * A Solid component that allows you to subscribe to the batcher state.\n   *\n   * This is useful for tracking specific parts of the batcher state\n   * deep in your component tree without needing to pass a selector to the hook.\n   *\n   * @example\n   * <batcher.Subscribe selector={(state) => ({ size: state.size, isExecuting: state.isExecuting })}>\n   *   {(state) => (\n   *     <div>Batch: {state().size} items, {state().isExecuting ? 'Executing...' : 'Idle'}</div>\n   *   )}\n   * </batcher.Subscribe>\n   */\n  Subscribe: <TSelected>(props: {\n    selector: (state: AsyncBatcherState<TValue>) => TSelected\n    children: ((state: Accessor<TSelected>) => JSX.Element) | JSX.Element\n  }) => JSX.Element\n  /**\n   * Reactive state that will be updated when the batcher state changes\n   *\n   * Use this instead of `batcher.store.state`\n   */\n  readonly state: Accessor<Readonly<TSelected>>\n  /**\n   * @deprecated Use `batcher.state` instead of `batcher.store.state` if you want to read reactive state.\n   * The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.\n   * Although, you can make the state reactive by using the `useSelector` in your own usage.\n   */\n  readonly store: Store<Readonly<AsyncBatcherState<TValue>>>\n}\n\n/**\n * Creates a Solid-compatible AsyncBatcher instance for managing asynchronous batches of items, exposing Solid signals for all stateful properties.\n *\n * This is the async version of the createBatcher hook. Unlike the sync version, this async batcher:\n * - Handles promises and returns results from batch executions\n * - Provides error handling with configurable error behavior\n * - Tracks success, error, and settle counts separately\n * - Has state tracking for when batches are executing\n * - Returns the result of the batch function execution\n *\n * Features:\n * - Configurable batch size and wait time\n * - Custom batch processing logic via getShouldExecute\n * - Event callbacks for monitoring batch operations\n * - Error handling for failed batch operations\n * - Automatic or manual batch processing\n * - All stateful properties (items, counts, etc.) are exposed as Solid signals for reactivity\n *\n * The batcher collects items and processes them in batches based on:\n * - Maximum batch size (number of items per batch)\n * - Time-based batching (process after X milliseconds)\n * - Custom batch processing logic via getShouldExecute\n *\n * Error Handling:\n * - If an `onError` handler is provided, it will be called with the error and batcher instance\n * - If `throwOnError` is true (default when no onError handler is provided), the error will be thrown\n * - If `throwOnError` is false (default when onError handler is provided), the error will be swallowed\n * - Both onError and throwOnError can be used together; the handler will be called before any error is thrown\n * - The error state can be checked using the underlying AsyncBatcher instance\n *\n * ## State Management and Selector\n *\n * The hook uses TanStack Store for reactive state management. You can subscribe to state changes\n * in two ways:\n *\n * **1. Using `batcher.Subscribe` component (Recommended for component tree subscriptions)**\n *\n * Use the `Subscribe` component to subscribe to state changes deep in your component tree without\n * needing to pass a selector to the hook. This is ideal when you want to subscribe to state\n * in child components.\n *\n * **2. Using the `selector` parameter (For hook-level subscriptions)**\n *\n * The `selector` parameter allows you to specify which state changes will trigger reactive updates\n * at the hook level, optimizing performance by preventing unnecessary updates when irrelevant\n * state changes occur.\n *\n * **By default, there will be no reactive state subscriptions** and you must opt-in to state\n * tracking by providing a selector function or using the `Subscribe` component. This prevents unnecessary\n * updates and gives you full control over when your component tracks state changes.\n *\n * Available state properties:\n * - `errorCount`: Number of failed batch executions\n * - `executionCount`: Total number of batch execution attempts (successful + failed)\n * - `hasError`: Whether the last batch execution resulted in an error\n * - `isExecuting`: Whether a batch execution is currently in progress\n * - `items`: Array of items currently queued for batching\n * - `lastError`: The error from the most recent failed batch execution (if any)\n * - `lastResult`: The result from the most recent successful batch execution\n * - `settleCount`: Number of batch executions that have completed (successful or failed)\n * - `successCount`: Number of successful batch executions\n *\n * ## Unmount behavior\n *\n * By default, the primitive cancels any pending batch and aborts any in-flight execution when the owning component unmounts.\n * Abort only cancels underlying operations (e.g. fetch) when the abort signal from `getAbortSignal()` is passed to them.\n * Use the `onUnmount` option to customize this. For example, to flush pending work instead:\n *\n * ```tsx\n * const batcher = createAsyncBatcher(fn, {\n *   maxSize: 10,\n *   wait: 2000,\n *   onUnmount: (b) => b.flush()\n * });\n * ```\n *\n * Note: For async utils, `flush()` returns a Promise and runs fire-and-forget in the cleanup.\n * If your batch function updates Solid signals, those updates may run after the component has\n * unmounted, which can cause unexpected reactive updates. Guard your callbacks accordingly when\n * using onUnmount with flush.\n *\n * Example usage:\n * ```tsx\n * // Default behavior - no reactive state subscriptions\n * const asyncBatcher = createAsyncBatcher(\n *   async (items) => {\n *     const results = await Promise.all(items.map(item => processItem(item)));\n *     return results;\n *   },\n *   {\n *     maxSize: 10,\n *     wait: 2000,\n *     onSuccess: (result) => {\n *       console.log('Batch processed successfully:', result);\n *     },\n *     onError: (error) => {\n *       console.error('Batch processing failed:', error);\n *     }\n *   }\n * );\n *\n * // Opt-in to track items or isExecuting changes (optimized for UI updates)\n * const asyncBatcher = createAsyncBatcher(\n *   async (items) => {\n *     const results = await Promise.all(items.map(item => processItem(item)));\n *     return results;\n *   },\n *   { maxSize: 10, wait: 2000 },\n *   (state) => ({ items: state.items, isExecuting: state.isExecuting })\n * );\n *\n * // Opt-in to track error state changes (optimized for error handling)\n * const asyncBatcher = createAsyncBatcher(\n *   async (items) => {\n *     const results = await Promise.all(items.map(item => processItem(item)));\n *     return results;\n *   },\n *   { maxSize: 10, wait: 2000 },\n *   (state) => ({ hasError: state.hasError, lastError: state.lastError })\n * );\n *\n * // Add items to batch\n * asyncBatcher.addItem(newItem);\n *\n * // Manually execute batch\n * const result = await asyncBatcher.execute();\n *\n * // Access the selected state (will be empty object {} unless selector provided)\n * const { items, isExecuting } = asyncBatcher.state();\n * ```\n */\nexport function createAsyncBatcher<TValue, TSelected = {}>(\n  fn: (items: Array<TValue>) => Promise<any>,\n  options: SolidAsyncBatcherOptions<TValue, TSelected> = {},\n  selector: (state: AsyncBatcherState<TValue>) => TSelected = () =>\n    ({}) as TSelected,\n): SolidAsyncBatcher<TValue, TSelected> {\n  const mergedOptions = {\n    ...useDefaultPacerOptions().asyncBatcher,\n    ...options,\n  } as SolidAsyncBatcherOptions<TValue, TSelected>\n  const asyncBatcher = new AsyncBatcher<TValue>(\n    fn,\n    mergedOptions,\n  ) as unknown as SolidAsyncBatcher<TValue, TSelected>\n\n  asyncBatcher.Subscribe = function Subscribe<TSelected>(props: {\n    selector: (state: AsyncBatcherState<TValue>) => TSelected\n    children: ((state: Accessor<TSelected>) => JSX.Element) | JSX.Element\n  }) {\n    const selected = useSelector(asyncBatcher.store, props.selector, {\n      compare: shallow,\n    })\n\n    return typeof props.children === 'function'\n      ? props.children(selected)\n      : props.children\n  }\n\n  const state = useSelector(asyncBatcher.store, selector, { compare: shallow })\n\n  createEffect(() => {\n    onCleanup(() => {\n      if (mergedOptions.onUnmount) {\n        mergedOptions.onUnmount(asyncBatcher)\n      } else {\n        asyncBatcher.cancel()\n        asyncBatcher.abort()\n      }\n    })\n  })\n\n  return {\n    ...asyncBatcher,\n    state,\n  } as SolidAsyncBatcher<TValue, TSelected> // omit `store` in favor of `state`\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA4LA,SAAgB,mBACd,IACA,UAAuD,CAAC,GACxD,kBACG,CAAC,IACkC;CACtC,MAAM,gBAAgB;EACpB,GAAG,uBAAuB,CAAC,CAAC;EAC5B,GAAG;CACL;CACA,MAAM,eAAe,IAAI,aACvB,IACA,aACF;CAEA,aAAa,YAAY,SAAS,UAAqB,OAGpD;EACD,MAAM,WAAW,YAAY,aAAa,OAAO,MAAM,UAAU,EAC/D,SAAS,QACX,CAAC;EAED,OAAO,OAAO,MAAM,aAAa,aAC7B,MAAM,SAAS,QAAQ,IACvB,MAAM;CACZ;CAEA,MAAM,QAAQ,YAAY,aAAa,OAAO,UAAU,EAAE,SAAS,QAAQ,CAAC;CAE5E,mBAAmB;EACjB,gBAAgB;GACd,IAAI,cAAc,WAChB,cAAc,UAAU,YAAY;QAC/B;IACL,aAAa,OAAO;IACpB,aAAa,MAAM;GACrB;EACF,CAAC;CACH,CAAC;CAED,OAAO;EACL,GAAG;EACH;CACF;AACF"}

package/dist/async-batcher/index.cjs

@@ -1,11 +0,0 @@
-Object.defineProperty(exports, Symbol.toStringTag, { value: 'Module' });
-const require_createAsyncBatcher = require('./createAsyncBatcher.cjs');
-
-exports.createAsyncBatcher = require_createAsyncBatcher.createAsyncBatcher;
-var _tanstack_pacer_async_batcher = require("@tanstack/pacer/async-batcher");
-Object.keys(_tanstack_pacer_async_batcher).forEach(function (k) {
-  if (k !== 'default' && !Object.prototype.hasOwnProperty.call(exports, k)) Object.defineProperty(exports, k, {
-    enumerable: true,
-    get: function () { return _tanstack_pacer_async_batcher[k]; }
-  });
-});

package/dist/async-batcher/index.d.cts

@@ -1,3 +0,0 @@
-import { SolidAsyncBatcher, SolidAsyncBatcherOptions, createAsyncBatcher } from "./createAsyncBatcher.cjs";
-export * from "@tanstack/pacer/async-batcher";
-export { SolidAsyncBatcher, SolidAsyncBatcherOptions, createAsyncBatcher };

package/dist/async-debouncer/createAsyncDebouncer.cjs

@@ -1,151 +0,0 @@
-const require_PacerProvider = require('../provider/PacerProvider.cjs');
-let solid_js = require("solid-js");
-let _tanstack_solid_store = require("@tanstack/solid-store");
-let _tanstack_pacer_async_debouncer = require("@tanstack/pacer/async-debouncer");
-
-//#region src/async-debouncer/createAsyncDebouncer.ts
-/**
-* A low-level Solid hook that creates an `AsyncDebouncer` instance to delay execution of an async function.
-*
-* This hook is designed to be flexible and state-management agnostic - it simply returns a debouncer instance that
-* you can integrate with any state management solution (createSignal, etc).
-*
-* Async debouncing ensures that an async function only executes after a specified delay has passed since its last invocation.
-* Each new invocation resets the delay timer. This is useful for handling frequent events like window resizing
-* or input changes where you only want to execute the handler after the events have stopped occurring.
-*
-* Unlike throttling which allows execution at regular intervals, debouncing prevents any execution until
-* the function stops being called for the specified delay period.
-*
-* Unlike the non-async Debouncer, this async version supports returning values from the debounced 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 debounced function.
-*
-* Error Handling:
-* - If an `onError` handler is provided, it will be called with the error and debouncer 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 AsyncDebouncer 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 `debouncer.Subscribe` component (Recommended for component tree subscriptions)**
-*
-* Use the `Subscribe` component 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 reactive updates
-* at the hook level, optimizing performance by preventing unnecessary updates 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` component. This prevents unnecessary
-* updates and gives you full control over when your component tracks state changes.
-*
-* Available state properties:
-* - `canLeadingExecute`: Whether the debouncer can execute on the leading edge
-* - `executionCount`: Number of function executions that have been completed
-* - `hasError`: Whether the last execution resulted in an error
-* - `isPending`: Whether the debouncer is waiting for the timeout to trigger execution
-* - `isExecuting`: Whether an async function execution is currently in progress
-* - `lastArgs`: The arguments from the most recent call to maybeExecute
-* - `lastError`: The error from the most recent failed execution (if any)
-* - `lastResult`: The result from the most recent successful execution
-* - `status`: Current execution status ('disabled' | 'idle' | 'pending' | 'executing')
-*
-* ## Unmount behavior
-*
-* By default, the primitive cancels any pending execution and aborts any in-flight execution when the owning 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 debouncer = createAsyncDebouncer(fn, {
-*   wait: 500,
-*   onUnmount: (d) => d.flush()
-* });
-* ```
-*
-* Note: For async utils, `flush()` returns a Promise and runs fire-and-forget in the cleanup.
-* If your debounced function updates Solid signals, those updates may run after the component has
-* unmounted, which can cause unexpected reactive updates. Guard your callbacks accordingly when
-* using onUnmount with flush.
-*
-* @example
-* ```tsx
-* // Default behavior - no reactive state subscriptions
-* const { maybeExecute } = createAsyncDebouncer(
-*   async (query: string) => {
-*     const results = await api.search(query);
-*     return results;
-*   },
-*   { wait: 500 }
-* );
-*
-* // Opt-in to track isPending or isExecuting changes (optimized for loading states)
-* const debouncer = createAsyncDebouncer(
-*   async (query: string) => {
-*     const results = await api.search(query);
-*     return results;
-*   },
-*   { wait: 500 },
-*   (state) => ({ isPending: state.isPending, isExecuting: state.isExecuting })
-* );
-*
-* // Opt-in to track error state changes (optimized for error handling)
-* const debouncer = createAsyncDebouncer(
-*   async (searchTerm) => {
-*     const data = await searchAPI(searchTerm);
-*     return data;
-*   },
-*   {
-*     wait: 300,
-*     leading: true,   // Execute immediately on first call
-*     trailing: false, // Skip trailing edge updates
-*     onError: (error) => {
-*       console.error('API call failed:', error);
-*     }
-*   },
-*   (state) => ({ hasError: state.hasError, lastError: state.lastError })
-* );
-*
-* // Access the selected state (will be empty object {} unless selector provided)
-* const { isPending, isExecuting } = debouncer.state();
-* ```
-*/
-function createAsyncDebouncer(fn, options, selector = () => ({})) {
-	const mergedOptions = {
-		...require_PacerProvider.useDefaultPacerOptions().asyncDebouncer,
-		...options
-	};
-	const asyncDebouncer = new _tanstack_pacer_async_debouncer.AsyncDebouncer(fn, mergedOptions);
-	asyncDebouncer.Subscribe = function Subscribe(props) {
-		const selected = (0, _tanstack_solid_store.useSelector)(asyncDebouncer.store, props.selector, { compare: _tanstack_solid_store.shallow });
-		return typeof props.children === "function" ? props.children(selected) : props.children;
-	};
-	const state = (0, _tanstack_solid_store.useSelector)(asyncDebouncer.store, selector, { compare: _tanstack_solid_store.shallow });
-	(0, solid_js.createEffect)(() => {
-		(0, solid_js.onCleanup)(() => {
-			if (mergedOptions.onUnmount) mergedOptions.onUnmount(asyncDebouncer);
-			else {
-				asyncDebouncer.cancel();
-				asyncDebouncer.abort();
-			}
-		});
-	});
-	return {
-		...asyncDebouncer,
-		state
-	};
-}
-
-//#endregion
-exports.createAsyncDebouncer = createAsyncDebouncer;
-//# sourceMappingURL=createAsyncDebouncer.cjs.map

package/dist/async-debouncer/createAsyncDebouncer.cjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"createAsyncDebouncer.cjs","names":["useDefaultPacerOptions","AsyncDebouncer","useSelector","shallow"],"sources":["../../src/async-debouncer/createAsyncDebouncer.ts"],"sourcesContent":["import { AsyncDebouncer } from '@tanstack/pacer/async-debouncer'\nimport { shallow, useSelector } from '@tanstack/solid-store'\nimport { createEffect, onCleanup } from 'solid-js'\nimport { useDefaultPacerOptions } from '../provider/PacerProvider'\nimport type { Store } from '@tanstack/solid-store'\nimport type { Accessor, JSX } from 'solid-js'\nimport type {\n  AsyncDebouncerOptions,\n  AsyncDebouncerState,\n} from '@tanstack/pacer/async-debouncer'\nimport type { AnyAsyncFunction } from '@tanstack/pacer/types'\n\nexport interface SolidAsyncDebouncerOptions<\n  TFn extends AnyAsyncFunction,\n  TSelected = {},\n> extends AsyncDebouncerOptions<TFn> {\n  /**\n   * Optional callback invoked when the owning component unmounts. Receives the debouncer instance.\n   * When provided, replaces the default cleanup (cancel + abort); use it to call flush(), reset(), cancel(), add logging, etc.\n   */\n  onUnmount?: (debouncer: SolidAsyncDebouncer<TFn, TSelected>) => void\n}\n\nexport interface SolidAsyncDebouncer<\n  TFn extends AnyAsyncFunction,\n  TSelected = {},\n> extends Omit<AsyncDebouncer<TFn>, 'store'> {\n  /**\n   * A Solid component that allows you to subscribe to the debouncer state.\n   *\n   * This is useful for tracking specific parts of the debouncer state\n   * deep in your component tree without needing to pass a selector to the hook.\n   *\n   * @example\n   * <debouncer.Subscribe selector={(state) => ({ isPending: state.isPending, isExecuting: state.isExecuting })}>\n   *   {(state) => (\n   *     <div>{state().isPending ? 'Waiting...' : state().isExecuting ? 'Executing...' : 'Ready'}</div>\n   *   )}\n   * </debouncer.Subscribe>\n   */\n  Subscribe: <TSelected>(props: {\n    selector: (state: AsyncDebouncerState<TFn>) => TSelected\n    children: ((state: Accessor<TSelected>) => JSX.Element) | JSX.Element\n  }) => JSX.Element\n  /**\n   * Reactive state that will be updated when the debouncer state changes\n   *\n   * Use this instead of `debouncer.store.state`\n   */\n  readonly state: Accessor<Readonly<TSelected>>\n  /**\n   * @deprecated Use `debouncer.state` instead of `debouncer.store.state` if you want to read reactive state.\n   * The state on the store object is not reactive, as it has not been wrapped in a `useSelector` hook internally.\n   * Although, you can make the state reactive by using the `useSelector` in your own usage.\n   */\n  readonly store: Store<Readonly<AsyncDebouncerState<TFn>>>\n}\n\n/**\n * A low-level Solid hook that creates an `AsyncDebouncer` instance to delay execution of an async function.\n *\n * This hook is designed to be flexible and state-management agnostic - it simply returns a debouncer instance that\n * you can integrate with any state management solution (createSignal, etc).\n *\n * Async debouncing ensures that an async function only executes after a specified delay has passed since its last invocation.\n * Each new invocation resets the delay timer. This is useful for handling frequent events like window resizing\n * or input changes where you only want to execute the handler after the events have stopped occurring.\n *\n * Unlike throttling which allows execution at regular intervals, debouncing prevents any execution until\n * the function stops being called for the specified delay period.\n *\n * Unlike the non-async Debouncer, this async version supports returning values from the debounced function,\n * making it ideal for API calls and other async operations where you want the result of the `maybeExecute` call\n * instead of setting the result on a state variable from within the debounced function.\n *\n * Error Handling:\n * - If an `onError` handler is provided, it will be called with the error and debouncer instance\n * - If `throwOnError` is true (default when no onError handler is provided), the error will be thrown\n * - If `throwOnError` is false (default when onError handler is provided), the error will be swallowed\n * - Both onError and throwOnError can be used together - the handler will be called before any error is thrown\n * - The error state can be checked using the underlying AsyncDebouncer instance\n *\n * ## State Management and Selector\n *\n * The hook uses TanStack Store for reactive state management. You can subscribe to state changes\n * in two ways:\n *\n * **1. Using `debouncer.Subscribe` component (Recommended for component tree subscriptions)**\n *\n * Use the `Subscribe` component to subscribe to state changes deep in your component tree without\n * needing to pass a selector to the hook. This is ideal when you want to subscribe to state\n * in child components.\n *\n * **2. Using the `selector` parameter (For hook-level subscriptions)**\n *\n * The `selector` parameter allows you to specify which state changes will trigger reactive updates\n * at the hook level, optimizing performance by preventing unnecessary updates when irrelevant\n * state changes occur.\n *\n * **By default, there will be no reactive state subscriptions** and you must opt-in to state\n * tracking by providing a selector function or using the `Subscribe` component. This prevents unnecessary\n * updates and gives you full control over when your component tracks state changes.\n *\n * Available state properties:\n * - `canLeadingExecute`: Whether the debouncer can execute on the leading edge\n * - `executionCount`: Number of function executions that have been completed\n * - `hasError`: Whether the last execution resulted in an error\n * - `isPending`: Whether the debouncer is waiting for the timeout to trigger execution\n * - `isExecuting`: Whether an async function execution is currently in progress\n * - `lastArgs`: The arguments from the most recent call to maybeExecute\n * - `lastError`: The error from the most recent failed execution (if any)\n * - `lastResult`: The result from the most recent successful execution\n * - `status`: Current execution status ('disabled' | 'idle' | 'pending' | 'executing')\n *\n * ## Unmount behavior\n *\n * By default, the primitive cancels any pending execution and aborts any in-flight execution when the owning component unmounts.\n * Abort only cancels underlying operations (e.g. fetch) when the abort signal from `getAbortSignal()` is passed to them.\n * Use the `onUnmount` option to customize this. For example, to flush pending work instead:\n *\n * ```tsx\n * const debouncer = createAsyncDebouncer(fn, {\n *   wait: 500,\n *   onUnmount: (d) => d.flush()\n * });\n * ```\n *\n * Note: For async utils, `flush()` returns a Promise and runs fire-and-forget in the cleanup.\n * If your debounced function updates Solid signals, those updates may run after the component has\n * unmounted, which can cause unexpected reactive updates. Guard your callbacks accordingly when\n * using onUnmount with flush.\n *\n * @example\n * ```tsx\n * // Default behavior - no reactive state subscriptions\n * const { maybeExecute } = createAsyncDebouncer(\n *   async (query: string) => {\n *     const results = await api.search(query);\n *     return results;\n *   },\n *   { wait: 500 }\n * );\n *\n * // Opt-in to track isPending or isExecuting changes (optimized for loading states)\n * const debouncer = createAsyncDebouncer(\n *   async (query: string) => {\n *     const results = await api.search(query);\n *     return results;\n *   },\n *   { wait: 500 },\n *   (state) => ({ isPending: state.isPending, isExecuting: state.isExecuting })\n * );\n *\n * // Opt-in to track error state changes (optimized for error handling)\n * const debouncer = createAsyncDebouncer(\n *   async (searchTerm) => {\n *     const data = await searchAPI(searchTerm);\n *     return data;\n *   },\n *   {\n *     wait: 300,\n *     leading: true,   // Execute immediately on first call\n *     trailing: false, // Skip trailing edge updates\n *     onError: (error) => {\n *       console.error('API call failed:', error);\n *     }\n *   },\n *   (state) => ({ hasError: state.hasError, lastError: state.lastError })\n * );\n *\n * // Access the selected state (will be empty object {} unless selector provided)\n * const { isPending, isExecuting } = debouncer.state();\n * ```\n */\nexport function createAsyncDebouncer<\n  TFn extends AnyAsyncFunction,\n  TSelected = {},\n>(\n  fn: TFn,\n  options: SolidAsyncDebouncerOptions<TFn, TSelected>,\n  selector: (state: AsyncDebouncerState<TFn>) => TSelected = () =>\n    ({}) as TSelected,\n): SolidAsyncDebouncer<TFn, TSelected> {\n  const mergedOptions = {\n    ...useDefaultPacerOptions().asyncDebouncer,\n    ...options,\n  } as SolidAsyncDebouncerOptions<TFn, TSelected>\n  const asyncDebouncer = new AsyncDebouncer<TFn>(\n    fn,\n    mergedOptions,\n  ) as unknown as SolidAsyncDebouncer<TFn, TSelected>\n\n  asyncDebouncer.Subscribe = function Subscribe<TSelected>(props: {\n    selector: (state: AsyncDebouncerState<TFn>) => TSelected\n    children: ((state: Accessor<TSelected>) => JSX.Element) | JSX.Element\n  }) {\n    const selected = useSelector(asyncDebouncer.store, props.selector, {\n      compare: shallow,\n    })\n\n    return typeof props.children === 'function'\n      ? props.children(selected)\n      : props.children\n  }\n\n  const state = useSelector(asyncDebouncer.store, selector, {\n    compare: shallow,\n  })\n\n  createEffect(() => {\n    onCleanup(() => {\n      if (mergedOptions.onUnmount) {\n        mergedOptions.onUnmount(asyncDebouncer)\n      } else {\n        asyncDebouncer.cancel()\n        asyncDebouncer.abort()\n      }\n    })\n  })\n\n  return {\n    ...asyncDebouncer,\n    state,\n  } as SolidAsyncDebouncer<TFn, TSelected> // omit `store` in favor of `state`\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA8KA,SAAgB,qBAId,IACA,SACA,kBACG,CAAC,IACiC;CACrC,MAAM,gBAAgB;EACpB,GAAGA,6CAAuB,CAAC,CAAC;EAC5B,GAAG;CACL;CACA,MAAM,iBAAiB,IAAIC,+CACzB,IACA,aACF;CAEA,eAAe,YAAY,SAAS,UAAqB,OAGtD;EACD,MAAM,eAAWC,mCAAY,eAAe,OAAO,MAAM,UAAU,EACjE,SAASC,8BACX,CAAC;EAED,OAAO,OAAO,MAAM,aAAa,aAC7B,MAAM,SAAS,QAAQ,IACvB,MAAM;CACZ;CAEA,MAAM,YAAQD,mCAAY,eAAe,OAAO,UAAU,EACxD,SAASC,8BACX,CAAC;CAED,iCAAmB;EACjB,8BAAgB;GACd,IAAI,cAAc,WAChB,cAAc,UAAU,cAAc;QACjC;IACL,eAAe,OAAO;IACtB,eAAe,MAAM;GACvB;EACF,CAAC;CACH,CAAC;CAED,OAAO;EACL,GAAG;EACH;CACF;AACF"}