chrome-remote-interface
Advanced tools
chrome-remote-interface - npm Package Compare versions
Comparing version 0.24.2 to 0.24.3
@@ -265,3 +265,3 @@ #!/usr/bin/env node | ||
| program | ||
| .version(packageInfo.version) | ||
| .option('-v, --v', 'Show this module version') | ||
| .option('-t, --host <host>', 'HTTP frontend host') | ||
@@ -336,4 +336,8 @@ .option('-p, --port <port>', 'HTTP frontend port') | ||
| } else { | ||
| program.outputHelp(); | ||
| process.exit(1); | ||
| if (program.v) { | ||
| console.log(packageInfo.version); | ||
| } else { | ||
| program.outputHelp(); | ||
| process.exit(1); | ||
| } | ||
| } |
@@ -12,3 +12,3 @@ { | ||
| "homepage": "https://github.com/cyrus-and/chrome-remote-interface", | ||
| "version": "0.24.2", | ||
| "version": "0.24.3", | ||
| "repository": { | ||
@@ -15,0 +15,0 @@ "type": "git", |
@@ -50,4 +50,7 @@ chrome-remote-interface [](https://travis-ci.org/cyrus-and/chrome-remote-interface) | ||
| You may also want to take a look at the [FAQ]. | ||
| [wiki]: https://github.com/cyrus-and/chrome-remote-interface/wiki | ||
| [async-await-example]: https://github.com/cyrus-and/chrome-remote-interface/wiki/Async-await-example | ||
| [FAQ]: https://github.com/cyrus-and/chrome-remote-interface#faq | ||
@@ -835,2 +838,54 @@ Installation | ||
| FAQ | ||
| --- | ||
| ### Invoking `Domain.method` I obtain `Domain.method is not a function` | ||
| This means that the protocol descriptor that you are using does not contain | ||
| `Domain.method`. If you are sure that your Chrome instance supports such method | ||
| you can call it directly: | ||
| ```js | ||
| client.send('Domain.method', ...); | ||
| ``` | ||
| or *ask* Chrome the correct protocol descriptor: | ||
| ```js | ||
| CDP({remote: true}); | ||
| ``` | ||
| See [here](#chrome-debugging-protocol-versions) for more information. | ||
| ### Invoking `Domain.method` I obtain `Domain.method wasn't found` | ||
| This means that the protocol descriptor that you are using contains a method | ||
| that is not supported by your Chrome instance. Most likely this is because you | ||
| are trying to use a bleeding-edge feature, try to update to a newer Chrome | ||
| version. | ||
| See [here](#chrome-debugging-protocol-versions) for more information. | ||
| To inspect the correct protocol descriptor use: | ||
| ``` | ||
| $ chrome-remote-interface inspect --remote | ||
| ``` | ||
| ### Headless Chrome problems? | ||
| Bear in mind that `--headless` Chrome is relatively new and there are kinks (in | ||
| Chrome) that are being worked out. If you believe you have encountered a bug, | ||
| take a look at the open issues, especially [external issues]. | ||
| [external issues]: https://github.com/cyrus-and/chrome-remote-interface/issues?q=label%3A%22external+issue%22 | ||
| ### Why my program stalls or behave unexpectedly if I run Chrome in a Docker container? | ||
| This happens because the size of `/dev/shm` is set to 64MB by default in Docker | ||
| and may not be enough for Chrome to navigate certain web pages. | ||
| You can change this value by running your container with, say, | ||
| `--shm-size=256m`. | ||
| Contributors | ||
@@ -837,0 +892,0 @@ ------------ |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by0.18%
1004268
- Lines of code
- increased by0.02%
16026
- Number of lines in readme file
- increased by6.47%
905