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

gstack-browser

v0.1.0

Published

Lightweight local browser automation CLI for agent-driven QA.

Downloads

137

Readme

gstack-browser

This directory contains gstack-browser, a standalone Node + Playwright browser automation CLI used by gl-browse, gl-qa, gl-qa-only, and visual review skills.

Install dependencies for local development:

cd browse
npm install
npx playwright install chromium

Run it from this checkout:

./dist/browse help
./dist/browse goto http://localhost:3000
./dist/browse screenshot /tmp/page.png

Or install the published package globally:

npm i -g gstack-browser

Choosing Local vs Published

The resolver supports three knobs:

  • GSTACK_BROWSER_BIN=/absolute/path/to/browser: hard override.
  • GSTACK_BROWSER_PROVIDER=global: use gstack-browser or gstack-browse from PATH.
  • GSTACK_BROWSER_PROVIDER=local: use the checkout/state-local browse/dist/browse.

Default auto behavior prefers PATH first, then the local/state wrapper. This makes the published package the normal provider when installed globally.

For local package development, use npm's global link:

cd browse
npm install
npx playwright install chromium
npm link

After that, gstack-browser on PATH points at this checkout, so GSTACK_BROWSER_PROVIDER=global and the default auto mode both use the local linked package. To go back to the published package, unlink/reinstall with npm:

npm unlink -g gstack-browser
npm i -g gstack-browser

To bypass npm link entirely while working in this repo:

GSTACK_BROWSER_PROVIDER=local ./browse/bin/find-browse

The lite skill resolver checks, in order:

  1. GSTACK_BROWSER_BIN, if set.
  2. gstack-browser / gstack-browse on PATH, unless GSTACK_BROWSER_PROVIDER=local.
  3. $PROJECT/.gstack-lite/browse/dist/browse
  4. $GSTACK_LITE_HOME/browse/dist/browse

This first Node port focuses on headless local browser QA. It intentionally skips cookie import from installed browsers, Chrome side panel/extension workflows, headed handoff, and ngrok/pairing.