chrome-remote-interface
Advanced tools
Comparing version 0.24.4 to 0.24.5
@@ -44,4 +44,4 @@ #!/usr/bin/env node | ||
options.target = function (targets) { | ||
return targets.findIndex(function (target) { | ||
return target.id === target; | ||
return targets.findIndex(function (_target) { | ||
return _target.id === target; | ||
}); | ||
@@ -48,0 +48,0 @@ }; |
@@ -12,3 +12,3 @@ { | ||
"homepage": "https://github.com/cyrus-and/chrome-remote-interface", | ||
"version": "0.24.4", | ||
"version": "0.24.5", | ||
"repository": { | ||
@@ -15,0 +15,0 @@ "type": "git", |
@@ -909,2 +909,18 @@ chrome-remote-interface [![Build Status](https://travis-ci.org/cyrus-and/chrome-remote-interface.svg?branch=master)](https://travis-ci.org/cyrus-and/chrome-remote-interface) | ||
### How does this compare to Puppeteer? | ||
[Puppeteer] is an additional high-level API built upon the [Chrome Debugging | ||
Protocol] which, among the other things, may start and use a bundled version of | ||
Chromium instead of the one installed on your system. Use it if its API meets | ||
your needs as it would probably be easier to work with. | ||
chrome-remote-interface instead is just a general purpose 1:1 Node.js binding | ||
for the [Chrome Debugging Protocol]. Use it if you need all the power of the raw | ||
protocol, e.g., to implement your own high-level API. | ||
See [#240] for a more thorough discussion. | ||
[Puppeteer]: https://github.com/GoogleChrome/puppeteer | ||
[#240]: https://github.com/cyrus-and/chrome-remote-interface/issues/240 | ||
Contributors | ||
@@ -911,0 +927,0 @@ ------------ |
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
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
1005751
941