📄️ Agent
Extends: undici.Dispatcher
📄️ Class: BalancedPool
Extends: undici.Dispatcher
📄️ CacheStorage
Undici exposes a W3C spec-compliant implementation of CacheStorage and Cache.
📄️ Class: Client
Extends: undici.Dispatcher
📄️ Connector
Undici creates the underlying socket via the connector builder.
📄️ MIME Type Parsing
MIMEType interface
📄️ Cookie Handling
Cookie interface
📄️ Diagnostics Channel Support
Stability: Experimental.
📄️ Interface: DispatchInterceptor
Extends: Function
📄️ Dispatcher
Extends: events.EventEmitter
📄️ Errors
Undici exposes a variety of error objects that you can use to enhance your error handling.
📄️ Fetch
Undici exposes a fetch() method starts the process of fetching a resource from the network.
📄️ Class: MockAgent
Extends: undici.Dispatcher
📄️ Class: MockClient
Extends: undici.Client
📄️ MockErrors
Undici exposes a variety of mock error objects that you can use to enhance your mock error handling.
📄️ Class: MockPool
Extends: undici.Pool
📄️ Class: Pool
Extends: undici.Dispatcher
📄️ Class: PoolStats
Aggregate stats for a Pool or BalancedPool.
📄️ Class: ProxyAgent
Extends: undici.Dispatcher
📄️ Class: RetryHandler
Extends: undici.DispatcherHandlers
📄️ Class: WebSocket
⚠️ Warning: the WebSocket API is experimental.
📄️ Client Lifecycle
An Undici Client can be best described as a state machine. The following list is a summary of the various state transitions the Client will go through in its lifecycle. This document also contains detailed breakdowns of each state.