4 ms·

I really wish the Chrome remote debugger allowed multiple websocket connections. A while back I made chromesync [0] to automatically push changes to your local

by aidos 11y ago

I really wish the Chrome remote debugger allowed multiple websocket connections. A while back I made chromesync [0] to automatically push changes to your local files directly in to Chrome. It means you can work in your own editor (whichever it is) as normal and have your js updated on the fly. For me, it's a great way to develop SPAs. Unfortunately, all too often you need to inspect something in the Chrome dev tools - which causes issues because you can only have one debugger connected. Someone created a proxy to handle multiple connections [1] but it requires running the Dev Tools in a separate tab via the proxy too. You can make it all work but it's a lot of moving pieces. [0] https://github.com/aidos/chromesync https://github.com/aidos/chromesync [1] https://www.npmjs.com/package/ws-multi-proxy https://www.npmjs.com/package/ws-multi-proxy

Nemcue 11y ago
"I really wish the Chrome remote debugger allowed multiple websocket connections." You, me, and a ton of other people. It's the number 1 starred Dev-Tools issue[1], and has been for years now. I'm guessing it's a political issue since there has been no indication whatsoever towards providing a solution. It really is a big deal; there's a ton of potential applications if we could plug multiple things into a single page. I think spy.js only scratches the surface of what's possible in this space; and spy.js is pretty awesome (if only it wasn't dreadfully slow and tied to an IDE). [1] https://code.google.com/p/chromium/issues/detail?id=129539 https://code.google.com/p/chromium/issues/detail?id=129539
auchenberg 11y ago
Agreed. This is much needed for enabling other tools to be built in the RemoteDebug-ecosystem. I've recently started exploring what I could mean to have concurrent connections to browsers, and what kind of tools we could build. Realtime visual comparison is really exciting. See https://kenneth.io/blog/2015/07/02/concurrent-editing-and-real-time-visual-comparison-between-browsers-in-chrome-devtools-with-remotedebug-gateway/ https://kenneth.io/blog/2015/07/02/concurrent-editing-and-re...

by aidos 11y ago

Nemcue 11y ago

"I really wish the Chrome remote debugger allowed multiple websocket connections." You, me, and a ton of other people. It's the number 1 starred Dev-Tools issue[1], and has been for years now. I'm guessing it's a political issue since there has been no indication whatsoever towards providing a solution. It really is a big deal; there's a ton of potential applications if we could plug multiple things into a single page. I think spy.js only scratches the surface of what's possible in this space; and spy.js is pretty awesome (if only it wasn't dreadfully slow and tied to an IDE). [1] https://code.google.com/p/chromium/issues/detail?id=129539 https://code.google.com/p/chromium/issues/detail?id=129539

auchenberg 11y ago

Agreed. This is much needed for enabling other tools to be built in the RemoteDebug-ecosystem. I've recently started exploring what I could mean to have concurrent connections to browsers, and what kind of tools we could build. Realtime visual comparison is really exciting. See https://kenneth.io/blog/2015/07/02/concurrent-editing-and-real-time-visual-comparison-between-browsers-in-chrome-devtools-with-remotedebug-gateway/ https://kenneth.io/blog/2015/07/02/concurrent-editing-and-re...