I can't work out if this is actually normal behaviour.
I am using a slightly unusual setup but nothing complicated. Basically, I have Brunch, a few plugins (including browser-sync!), and I'm using vibe.d as a server (that's the unusual bit). Browsersync is set up in proxy mode and seems happy. When I open the browser window, I get a 'browser-sync connected' message and all watched files update immediately in the browser.
But I am getting requests hitting the server for the file ;
localhost:3000/browser-sync/browser-sync-client.2.18.13.js
And this file doesn't exist, resulting in a 404 (reported in the browser console and in the server log).
The request for this file is coming from the script 'browser-sync-injector.js', according to my browser console.
I notice that browsersync in the browser also requests the file ;
localhost:3000/browser-sync/browser-sync-client.js?v=2.18.13
But this request doesn't even reach my server - I presume it is intercepted and dealt with by the browsersync proxy? In fact, this file is served to the browser even if I shutdown the vibe.d server so the only place it can be coming from is the proxy server.
Are those two files that are being requested two alternative ways of requesting the same file, one of which will work, and the other is supposed to fail?
The only browser-sync feature that doesn't seem to be working here is synced scrolling across connected browsers (which doesn't really bother me much). I have no idea if this is linked to the above missing file.
I can't work out if this is actually normal behaviour.
I am using a slightly unusual setup but nothing complicated. Basically, I have Brunch, a few plugins (including browser-sync!), and I'm using vibe.d as a server (that's the unusual bit). Browsersync is set up in proxy mode and seems happy. When I open the browser window, I get a 'browser-sync connected' message and all watched files update immediately in the browser.
But I am getting requests hitting the server for the file ; localhost:3000/browser-sync/browser-sync-client.2.18.13.js And this file doesn't exist, resulting in a 404 (reported in the browser console and in the server log). The request for this file is coming from the script 'browser-sync-injector.js', according to my browser console.
I notice that browsersync in the browser also requests the file ; localhost:3000/browser-sync/browser-sync-client.js?v=2.18.13 But this request doesn't even reach my server - I presume it is intercepted and dealt with by the browsersync proxy? In fact, this file is served to the browser even if I shutdown the vibe.d server so the only place it can be coming from is the proxy server.
Are those two files that are being requested two alternative ways of requesting the same file, one of which will work, and the other is supposed to fail?
The only browser-sync feature that doesn't seem to be working here is synced scrolling across connected browsers (which doesn't really bother me much). I have no idea if this is linked to the above missing file.
So, is this normal or should I fix it?