chrome-pool - npm Package Compare versions

Comparing version 1.0.9 to 1.0.10

package.json

		{
		"name": "chrome-pool",
		"version": "1.0.9",
		"version": "1.0.10",
		"description": "headless chrome tabs manage pool",
		@@ -26,3 +26,3 @@ "keywords": [
		"chrome-remote-interface": "^0.23.2",
		"chrome-runner": "^1.1.0"
		"chrome-runner": "^1.1.1"
		},
		@@ -29,0 +29,0 @@ "devDependencies": {

README.md

		@@ -11,6 +11,6 @@ [![Npm Package](https://img.shields.io/npm/v/chrome-pool.svg?style=flat-square)](https://www.npmjs.com/package/chrome-pool)
		## Use
		1. install from npm by `npm i chrome-pool`
		#### 1. install from npm by `npm i chrome-pool`


		2. start ChromePool:
		#### 2. start ChromePool:
		```js
		@@ -33,3 +33,3 @@ const ChromePool = require('chrome-pool');

		3. require a tab to use:
		#### 3. require a tab to use:
		```js
		@@ -46,3 +46,3 @@ // require a free tab from pool to use

		4. use protocol to control tab:
		#### 4. use protocol to control tab:
		```js
		@@ -54,3 +54,3 @@ const { Page,Target,Network,...} = protocol;

		5. after use a tab release it to pool:
		#### 5. after use a tab release it to pool:
		```js
		@@ -62,3 +62,3 @@ chromeTabsPoll.release(tabId);

		6. show chrome
		#### 6. show chrome
		In dev time, you may want to know what chrome are doing rather than let chrome run in headless.
		@@ -65,0 +65,0 @@ You can set env `SHOW_CHROME=true` when run your nodejs app to disable headless to debug chrome.

New alerts