chrome-remote-multiplex icon indicating copy to clipboard operation
chrome-remote-multiplex copied to clipboard

Allows multiple Chrome DevTools Clients to simultaneously connect to a single Remote Debugger (ie Chrome Headless) instance

Results 4 chrome-remote-multiplex issues
Sort by recently updated
recently updated
newest added

I believe this project may not be necessary any longer: https://developers.google.com/web/updates/2017/10/devtools-release-notes#multi-client Give it a whirl and file bugs if there are any inconsistencies.

I'd like to be able to run a large number of chrome browsers behind a load balancer.

There seems to be some repeated work between chrome-remote-multiplex and crmux: https://npmcompare.com/compare/chrome-remote-multiplex,crmux It would be good for you, @johnspackman, and @sidorares to work together on one module.

The DOM Domain needs to filter events so only events about DOM nodes which are already known to the client are passed forward Pointed out by @cyrus-and here https://github.com/cyrus-and/chrome-remote-interface/issues/217#issuecomment-317989354