CodeVetter · Repo Unpack · Extension points
mswjs/msw
The experimental API exposes the same source/frame abstractions used by the built-in environments. Handler factories, custom predicates, controllers, and sibling graphs provide additional composition boundaries. WebSocket extensions can change both runtime messages and inferred APIs. Storage implementations and Vite hooks are identifiable implementation seams, with public export/build configuration determining what consumers can import.
- msw/experimental exports defineNetwork, NetworkSource, InterceptorSource, NetworkFrame, protocol frames, and handler controllers; a custom source implements enable and queues frames through an awaited emitter.
- Custom NetworkFrame subclasses define protocol/data, handler selection, resolve, passthrough, errorWith, and unhandled diagnostics; resolve reports handled, unhandled, or skipped with true/false/null.
- RequestHandler subclasses supply predicate/log and may override parse/extendResolverArgs; http's createHttpHandler factory constructs HttpHandler while custom HTTP predicates can calculate resolver params.
- HandlersController abstracts getState/setState and supplies grouped use/reset/restore/dispose operations; AsyncHandlersController changes state ownership using AsyncLocalStorage rather than replacing request resolution.
- attachSiblingHandlers composes hidden transport/upgrade handlers with a public owner; grouping recursively visits sibling graphs and deduplicates references, while listHandlers hides implementation siblings.
- WebSocketExtension is publicly re-exported; ws.link accepts ordered extensions, handler.run invokes apply and extend, and ws.onUpgrade is read at request time so later overrides affect existing links.
- onUnhandledFrame accepts an async callback receiving frame and defaults; predefined strategies suppress common HTTP assets, while custom callbacks must apply their own asset policy and defaults.error only prints.
- WebSocketClientStore defines add/getAll/deleteMany with memory/IndexedDB implementations selected by the manager; new public utility modules are automatically discovered by tsdown and exposed through the ./utils/* export.