The development socket appears to use window.location.host, so attempts to connect to e.g. https://vagrant.local/sockjs-node/info?t=1609278734724 instead of the correct host.
The old version of react-wp-scripts had a specific workaround for this IIRC.
The development socket appears to use window.location.host, so attempts to connect to e.g.
https://vagrant.local/sockjs-node/info?t=1609278734724
instead of the correct host.The old version of react-wp-scripts had a specific workaround for this IIRC.