Missing global requestTimeout configuration in Remix loaders and actions

Confirmed facts

Remix passes an request.signal (AbortSignal) to every loader and action. The framework does not provide a built‑in global requestTimeout option.

Likely explanation

To abort work after a fixed duration you must create your own abort signal and combine it with the navigation signal. The recommended way is to use AbortController.timeout() (or a polyfill) and then AbortSignal.any([request.signal, timeoutSignal]).

Steps to add a per‑route timeout

1. In the route file, export a constant (e.g., export const REQUEST_TIMEOUT = 8000;) representing milliseconds.
2. Create a helper function that wraps a loader/action:

import type { LoaderFunction, ActionFunction } from '@remix-run/node';

function withTimeout<T extends LoaderFunction | ActionFunction>(
  handler: T,
  timeoutMs: number
) {
  return async (...args: Parameters<T>) => {
    const [request, ...rest] = args;
    const timeoutSignal = AbortController.timeout(timeoutMs);
    const combinedSignal = AbortSignal.any([request.signal, timeoutSignal]);
    // eslint-disable-next-line @typescript-eslint/no-unsafe-assignment
    const modifiedRequest = new Request(request, { signal: combinedSignal });
    return handler(modifiedRequest, ...rest);
  };
}

3. Apply the wrapper:

export const loader = withTimeout(async ({ request }) => {
  // your loader logic – it will receive the combined signal
  await db.query(...);
  return json({ data });
}, REQUEST_TIMEOUT);

4. Repeat for actions if needed.

Global timeout option (optional)

If you prefer a single value for all routes, add it to remix.config.js:

// remix.config.js
export default {
  // …other config
  requestTimeout: 12000, // milliseconds
};

Then create a generic wrapper that reads this value:
import remixConfig from './remix.config';

export function withGlobalTimeout<T extends LoaderFunction | ActionFunction>(handler: T) {
  const timeoutMs = remixConfig.requestTimeout ?? 0;
  return timeoutMs > 0 ? withTimeout(handler, timeoutMs) : handler;
}

Apply withGlobalTimeout to each loader/action, or use a plugin to automate the wrapping.
Interaction with existing request.signal
The combined signal from AbortSignal.any aborts when either the navigation signal fires or the timeout expires. No double‑cancellation occurs because the underlying operation receives a single signal; both sources simply set the same abort flag.
Missing diagnostic detail
To confirm that AbortController.timeout is available without a polyfill, please specify the Node.js version you are targeting (or whether you intend to polyfill). If you are on Node < 16, a polyfill will be required and the steps above remain the same, only the import changes.