Dev Proxy v2.1 Introduces Configuration Hot Reload and Stdio Traffic Proxying
Briefly

Dev Proxy v2.1 Introduces Configuration Hot Reload and Stdio Traffic Proxying
"One of the main additions in Dev Proxy v2.1 is configuration hot reload. The proxy now watches the configuration file and automatically restarts when changes are saved. This removes the need for manual restarts during development. According to the maintainers, this feature addresses a long-standing request from the community and is intended to make it easier to adjust settings such as mock responses, error rates, plugins, or URL patterns while keeping the development flow uninterrupted."
"Dev Proxy can now intercept, inspect, and mock standard input, output, and error streams. This capability is designed to support tools that communicate over stdio, including Model Context Protocol (MCP) servers and similar utilities. By wrapping an executable with Dev Proxy, developers can view stdio traffic in familiar browser tooling, simulate latency, and return mocked responses. This expands the scope of Dev Proxy beyond HTTP-based scenarios and enables testing and debugging of a wider range of applications."
Dev Proxy v2.1 introduces configuration hot reload that watches the configuration file and automatically restarts when changes are saved, eliminating manual restarts and easing adjustments to mock responses, error rates, plugins, and URL patterns. The release adds stdio traffic proxying to intercept, inspect, and mock standard input, output, and error streams, enabling testing of MCP servers and other stdio tools by wrapping executables and viewing traffic in browser tooling, simulating latency, and returning mocked responses. A new CLI option allows direct API port configuration. The LatencyPlugin supports delays longer than ten seconds. The web API permits cross-origin requests. Several bug fixes are included.
Read at InfoQ
Unable to calculate read time
[
|
]