chrome-remote-interface - npm Package Compare versions

Comparing version 0.33.0 to 0.33.2

package.json

		@@ -18,3 +18,3 @@ {
		"homepage": "https://github.com/cyrus-and/chrome-remote-interface",
		"version": "0.33.0",
		"version": "0.33.2",
		"repository": {
		@@ -21,0 +21,0 @@ "type": "git",

README.md

		@@ -5,5 +5,2 @@ # chrome-remote-interface

		[Build Status]: https://app.travis-ci.com/cyrus-and/chrome-remote-interface.svg?branch=master
		[travis]: https://app.travis-ci.com/cyrus-and/chrome-remote-interface

		[Chrome Debugging Protocol] interface that helps to instrument Chrome (or any
		@@ -137,11 +134,11 @@ other suitable [implementation](#implementations)) by providing a simple

		Plug the device and enable the [port forwarding][adb], for example:
		Plug the device and make sure to authorize the connection from the device itself. Then
		enable the port forwarding, for example:

		adb forward tcp:9222 localabstract:chrome_devtools_remote
		adb -d forward tcp:9222 localabstract:chrome_devtools_remote

		Note that in Android, Chrome does not have its own protocol available, a local
		version must be used. See [here](#chrome-debugging-protocol-versions) for more information.
		After that you should be able to use `http://127.0.0.1:9222` as usual, but note that in
		Android, Chrome does not have its own protocol available, so a local version must be used.
		See [here](#chrome-debugging-protocol-versions) for more information.

		[adb]: https://developer.chrome.com/devtools/docs/remote-debugging-legacy

		##### WebView
		@@ -148,0 +145,0 @@

LICENSE

Sorry, the diff of this file is not supported yet

New alerts