Serve Chrome Dev Tools remotley

[andysterland]

This issue tracks adding support to host the Chrome Dev Tools (that works with the adapter!) frontend remotely from the adapter.

[auchenberg]

I just had a look at the source, and it seems like you are starting Chrome with remote debugging enabled in order to serve the front-end, right?

That's strictly not needed, as Chrome has a internal URL which can be used to open DevTools: chrome-devtools://devtools/bundled/devtools.html?ws=<webSocketUrl>&remoteFrontend=true'

However the drawback is that it's a "chrome url", which means you can't redirect to it, for security reasons, so the user would have to copy&paste the URL.

[lucaspiller]

Currently you can access the target list "http://:9222/" remotely, and when you click on a target it redirects to the dev tools at "localhost:9223" which doesn't work. If the client is remote, it would be good to have something saying to use this URL instead (even if you have to copy and paste it).