Comments (4)
From @paulirish on August 7, 2017 18:12
Thanks for filing this. I looked into it and found that we have two options:
- Chrome will now log this target to stderr on launch. Previous to this CL, we'd see something like this:
DevTools listening on 127.0.0.1:56296
and it now prints:
DevTools listening on ws://127.0.0.1:63126/devtools/browser/c07d6691-cfb8-4a88-9bff-a03ce85848ea
- If chrome is launched with the remote-debugging-port=0, then it creates a
DevToolsActivePort
file in the user profile directory. (This doesn't happen if port is non-zero). It's contents are now both the port and the browser WS target URL:
56778
/devtools/browser/7ef11f4e-5c38-4111-8a7c-979703b95d00
We had plans to use Chrome's magic port=0 resolution already, so I'm thinking we'll do adopt the first option.
@joelgriffith As for exposing to users, how about the instance object (with the kill()
method) gets a property called browserWs
with this url?
from chrome-launcher.
From @joelgriffith on August 7, 2017 18:20
browserWs
would be fantastic! Thanks!
from chrome-launcher.
From @paulirish on August 16, 2017 0:40
I have an impl nearly ready for this in https://github.com/GoogleChrome/lighthouse/compare/browserws
from chrome-launcher.
I think this has become more desirable with the puppet release as it (I'm assuming) can connect to the browser-level target via
puppeteer.connect({ 'browserWSEndpoint': 'ws://localhost:51378/devtools/browser/id' })
from chrome-launcher.
Related Issues (20)
- crash when launch with remote debugging pipe
- Reuse an existing window HOT 1
- RangeError [ERR_FS_FILE_TOO_LARGE]: File size (3055630622) is greater than 2 GiB
- Chrome launcher wont launch HOT 1
- Beta and Dev channels are not detected
- igmore
- /Users/sample/node_modules/chrome-launcher/dist/chrome-finder.js:14 const log = require('lighthouse-logger'); ^ Error [ERR_REQUIRE_ESM]: require() of ES Module HOT 1
- Unknown error when ChromeLauncher.launch() in worker thread HOT 1
- Version v0.15.2 and kill chrome instance HOT 3
- Update readme for 1.0.0: ERR_REQUIRE_ESM
- `prefs` option doesn't work HOT 3
- Issue determining temp dir path HOT 1
- flag for setting useragentdata
- How to access environments variable with JS in chrome?
- move the red error dot to the console tab where it belongs HOT 1
- Add `--enable/disable-features=ChromeRootStoreUsed` flag HOT 2
- `user-data-dir` improperly replaced with Win32 path when running in WSL
- prefs option is incorrectly treated as a flat Record<string,JSONLike>, nested objects are not merged but overwritten HOT 1
- Search-engine dialog HOT 4
- 1.1.2 Tag missing HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from chrome-launcher.