import type { ErrorContext } from './types';
/**
 * Pull the structured `{ code, data, message, issues, status }` out of whatever
 * the caller caught. An authup server error arrives as a hapic `ClientError`
 * whose `response.data` is the serialized error body (`AuthupError.toJSON`
 * flattens `code` + `data` onto the top level and carries the validup
 * `issues`); a directly-thrown `AuthupError` or plain `Error` exposes the
 * same fields on itself. Duck-typed on purpose — no hapic import (it is not a
 * declared dependency, and its `isClientError` guard is `instanceof`-based, so
 * it would miss a non-hapic-instance error), works for both transports.
 */
export declare function extractErrorContext(error: unknown): ErrorContext;
//# sourceMappingURL=module.d.ts.map