• Requires fix(WebSocket): resolve relative connection urls interceptors#763

Looks like ws.link() doesn't resolve relative URLs against the page's origin. The logic is there on MSW side, but Interceptors throw on relative WebSocket URLs because it never resolves them according to the specification.

Our logic didn't account that the WebSocket constructor will enforce the ws/wss scheme on the actual URL. Since a relative handler URL is resolved against location.href, it always produced a mismatch.

ws.link('/api') // "http://localhost/api"
new WebSocket('/api') // "ws://localhost/api"

We are now correctly resolving relative paths in the ws.link before passing them to the URL matching.