Discussion: use Undici

[sebastien-comeau]

Environment

Node version: v18 and newer
typed-rest-client version: Latest

Issue Description

I'm eager to leverage typed-rest-client within my Remix application. However, I believe its current reliance on http and https limits its potential for certain advanced features.

Specifically, I'm interested in incorporating:

• Retry mechanisms (RetryAgent)
• Global and request dispatchers (Dispatcher)

These features can be more effectively managed with undici.

I'm considering forking the repository to implement this transition. I'd appreciate your insights on the feasibility and potential implications of such a change.

[sebastien-comeau]

Anyone?

[KonstantinTyukalov]

Hi @sebastien-comeau, thanks for the reporting! We are working on higher priority issues now, but we'll get back to this one once we'll have capacity.

Note that this client is currently supporting node 16, so to add the undici features we'll need to drop the node 16 support.

Regarding retries, we currently have simple built-in retry logic:

typed-rest-client/lib/Interfaces.ts

Lines 57 to 59 in 92f407b

	// Allows retries only on Read operations (since writes may not be idempotent)
	allowRetries?: boolean;
	maxRetries?: number;

Also note that the main goal of the typed-rest-client package is to provide RESTful request-response wrappers, so it wasn't designed for 'fire-and-forget' (am I right that this is something undici's Dispatcher do?) use cases initially