ProxyTargetDetailed typing requires host/port even when using socketPath (Unix socket)

[ooopus]

Problem

When using Vite dev server proxy with a Unix domain socket, I want to set:
target: { socketPath: "/path/to/backend.sock" }

But TypeScript typing for ProxyTargetDetailed requires host and port, so { socketPath } alone fails type-checking.

Expected

Allow a Unix socket target without requiring host/port. In Node.js HTTP request options, socketPath is meant to be used as an alternative to host:port ("use one of host:port or socketPath"). This is a mutually exclusive choice.

Actual

TypeScript reports that host and port are missing.

[williamstein]

This change seems reasonable to me.

[sapphi-red]

It makes sense to me as well. I think it would be helpful if there's a JSDoc comment that clarifies that either host + port or socketPath is required.