Playground

This page runs the actual @ylcnfrht/enhanced-abort-controller source in your browser. Pick an example or write your own, then press Run. console.log output and uncaught errors appear on the right. Copy link puts the snippet in the URL so you can share it.

Example

TypeScript code

import { EnhancedAbortController, TimeSpan, isAbortError, isTimeoutError } from '@ylcnfrht/enhanced-abort-controller';

/** Stands in for fetch: resolves after ms, rejects with signal.reason on abort. */
function work(ms: number, signal: AbortSignal): Promise<string> {
  return new Promise((resolve, reject) => {
    signal.throwIfAborted();
    const timer = setTimeout(() => resolve(`done after ${ms} ms`), ms);
    signal.addEventListener('abort', () => (clearTimeout(timer), reject(signal.reason)), { once: true });
  });
}

async function attempt(ms: number, cancelAfter?: number) {
  const controller = new EnhancedAbortController().abortAfter(TimeSpan.fromMilliseconds(300));
  if (cancelAfter !== undefined) setTimeout(() => controller.abort(), cancelAfter);
  try {
    console.log(await work(ms, controller.signal));
  } catch (error) {
    if (!isAbortError(error)) throw error;
    console.log(isTimeoutError(error) ? 'timed out' : 'cancelled', '·', error);
  } finally {
    controller.dispose(); // releases the timer; does not abort
  }
}

await attempt(100);
await attempt(1000);
await attempt(1000, 50);

Console

Press Run (or ⌘/Ctrl + Enter).

Types are stripped, not checked, here (Sucrase). The library itself is the real @ylcnfrht/enhanced-abort-controller source. Output that arrives after the snippet returns (timers, aborts) keeps appearing. using needs a browser with explicit resource management (Chrome 134+); elsewhere callcontroller.dispose(). In Node a pending abortAfter alone does not keep the process alive; a browser tab has no such notion, so here it simply fires.