npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

chrome-pool

v1.2.1

Published

headless chrome tabs manage pool

Readme

Npm Package Build Status Dependency Status Npm Downloads

chrome-pool

Headless chrome tabs manage pool, concept come from database connection pool for reuse chrome tab improve performance.

Use

1. install from npm by npm i chrome-pool

2. start ChromePool:

const ChromePool = require('chrome-pool');

const chromePoll = await ChromePool.new(options);
await chromePoll.destroyPoll();

await ChromePool.new() will make a new ChromePool and start a new chrome. A ChromePool means a chrome.

static method new() support options:

  • maxTab: {number} max tab to render pages, default is no limit.

  • port: {number} chrome debug port, default is random a free port.

  • chromeRunnerOptions: {object} options from chrome-runner and will pass to chrome-runner when launch chrome

  • protocols: {array} require chrome devtool protocol to be enable before use. e.g ['Network','Log'].

await chromePoll.destroyPoll() can release all resource used by this pool, kill chrome.

3. require a tab to use:

// require a free tab from pool to use
const { tabId,protocol } = await chromeTabsPoll.require();
// tabId
const { Page,Target,Network,...} = protocol;

await chromeTabsPoll.require() will return a object with prop:

  • tabId: chrome tab id.

  • protocol: chrome remote control protocol.

4. use protocol to control tab:

const { Page,Target,Network,...} = protocol;

protocol detail use see chrome-devtools-protocol doc. all protocol required be enable before use has been enable by chrome-pool.

5. after use a tab release it to pool:

await chromeTabsPoll.release(tabId);

release will release all resource used by this tab include removeAllListeners, so you don't need to removeListener by yourself. By default release will navigate tab to about:blank to reduce chrome resource use, you can close this feature by call chromeTabsPoll.release(tabId,false)

6. show chrome

In dev time, you may want to know what chrome are doing rather than let chrome run in headless. You can set env SHOW_CHROME=true when run your nodejs app to disable headless to debug chrome.

see test for more use case.

Notice chrome 59+ must install on you system

Friends