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

devtools-active-port

v1.0.0

Published

Resolve DevToolsActivePort for Chromium-based browsers

Readme

devtools-active-port

Zero-config active DevTools port resolution for Chromium-based browsers.

Why

Opening the WebSocket at DevToolsActivePort automatically triggers a consent dialog users can click through to enable remote debugging on demand. No restart, command line flags or other configuration is necessary, just read the file and go.

How

Searches default user data directories for Chrome, Edge, Brave, Opera, and others across macOS, Linux, and Windows to parse the active port and WebSocket path. Auto-discovers whatever browser is currently running, or targets a specific browser / profile by name or path.

Usage

import resolveDevToolsActivePort from 'devtools-active-port'

// Auto-detect active debugging port across all known browsers
const info = resolveDevToolsActivePort()
// => { port: 9222, path: 'devtools/browser/6b579178-...' }

// Or specify a browser (case, spaces, and hyphens are normalized)
const edgeInfo = resolveDevToolsActivePort('Microsoft Edge')

// Or specify a custom user data directory
const customInfo = resolveDevToolsActivePort({ userDataDir: '/path/to/profile' })

Options

Pass an options object or browser name string:

  • browser: Target a specific browser by name or alias (e.g. 'Google Chrome', 'msedge', 'brave').
  • userDataDir: Path to a custom user data directory containing DevToolsActivePort (overrides browser).

If no options are passed, standard paths for all supported browsers are checked in order.

Supported Browsers

  • Google Chrome (chrome, google-chrome)
  • Google Chrome Canary (canary, chrome-canary, chrome-sxs)
  • Chromium (chromium)
  • Microsoft Edge (edge, msedge, microsoft-edge)
  • Brave Browser (brave, brave-browser)
  • Arc (arc)
  • Vivaldi (vivaldi)
  • Opera & Opera GX (opera, operagx)

License

MIT