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-tab

v4.0.0

Published

Sugar for Chrome's devtools protocol

Readme

chrome-tab

Sugar for Chrome's devtools protocol.

Why

chrome-devtools-mcp crashed my machine. The issue appears to worsen with the number of tabs, and I have far too many of those. Raw CDP isn't smooth either as there is currently no straightforward way to get a page session for an active tab, also Chrome's JSON-RPC layer diverged from spec (sessionId outside params, demanding numeric message IDs, etc).

How

  • Auto-discovers your running Chromium-based browser on macOS, Linux, and Windows. No flags or restarts.
  • Workaround for cleanly finding active tabs / pages / sessionIds.
  • stdio based MCP server with just a pinch of sugar, dumb proxy for everything else.

Usage

import Chrome from 'chrome-tab'

// Connect to Chrome's root debugging port (auto-discovers port or defaults to 9222)
const browser = new Chrome()
await browser.connect()

// List open active tabs (default)
const tabs = await browser.listTabs()
const targetId = tabs[0].targetId

// Attach to the tab to obtain its page sessionId
const sessionId = await browser.attachTab(targetId)

// Run JavaScript in that tab session
const { result } = await browser.call('Runtime.evaluate', {
	expression: 'document.title',
	returnByValue: true
}, sessionId)

// Navigate that tab session
await browser.call('Page.navigate', { url: 'https://github.com' }, sessionId)

// Capture screenshot
const { data } = await browser.call('Page.captureScreenshot', {}, sessionId)

MCP

Config

{
	"mcpServers": {
		"chrome-tab": {
			"command": "npx",
			"args": ["-y", "chrome-tab"]
		}
	}
}

Options

  • --browser, -b or CHROME_BROWSER: Target a specific browser flavor (chrome, canary, chromium, edge, brave, arc, vivaldi, opera).
  • --user-data-dir or CHROME_USER_DATA_DIR: Discover the active port from a specific user data directory (overrides --browser).
  • --port, -p or CHROME_PORT: Connect directly to an explicit port (overrides --user-data-dir and --browser).
  • --host, -h or CHROME_HOST: Host to connect to (default: 127.0.0.1).
  • --path or CHROME_PATH: Custom WebSocket path.

Tools

  • list_tabs({ query? }) - Lists active tabs (one per window); pass query to search all including background tabs.
  • attach_tab({ targetId?, url? }) - Attaches to a tab by targetId, or pass url to open and attach. Sets it as default target.
  • eval({ expression, wait?, sessionId? }) - Evaluates JavaScript in REPL mode and returns the trailing expression value.
  • screenshot({ format?, quality?, sessionId? }) - Captures a screenshot of the tab.
  • call({ method, params?, sessionId? }) - Universal CDP passthrough for raw commands.

Security

Because chrome-tab attaches to your live browser and grants raw CDP access, it automatically inherits all of your authenticated sessions, cookies and other local storage along with full code execution privileges. Treat agent browser access like you would shell access. Hallucinations, mistakes and prompt injection are real, you've been warned!

License

MIT