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

@rent-scraper/browser-server

v1.0.32

Published

Local browser server to help scrape data for rental listings

Readme

@rent-scraper/browser-server

Local HTTP server wrapping Puppeteer. Runs at http://localhost:8082 and manages a persistent browser session for Zillow scraping — handling cookie capture, PerimeterX bot detection, and captcha solving.

Why a separate server?

The browser session (and its PerimeterX trust cookies) must persist across the full scrape run. Running Puppeteer inside the scrape process would restart the session on every zip code fetch. The server keeps the browser alive and exposes it over HTTP so the scraping process can read cookies and trigger actions without owning the browser lifecycle.

Endpoints

| Method | Path | Description | | ------ | --------------------- | ------------------------------------------------------------------------------------ | | GET | /server | Health check — returns { running: true } | | POST | /browser/launch | Launch the browser | | POST | /browser/open | Navigate to a URL, returns { status: 'navigated' \| 'captcha' \| 'not connected' } | | POST | /browser/status | Check current page status without navigating | | POST | /browser/close | Close the current page | | GET | /cookie | Return the current Zillow cookie string | | POST | /cookie/save | Extract and save the Zillow cookie from the browser session | | POST | /cookie/refresh | Re-extract cookie after a navigation | | POST | /cookie/redfin/save | Extract and save the Redfin cookie | | POST | /captcha/solve | Auto-solve a PerimeterX captcha via keyboard hold | | POST | /server/shutdown | Shut down the browser and stop the server |

Captcha Solving

PerimeterX uses a press-and-hold challenge (#px-captcha). The solver (solve-captcha.ts) presses Tab to focus the element, holds Space for 10 seconds, then reloads to verify. Retries up to 5 times with a 3-second pause between attempts.

Usage

# Start (production build)
pnpm run browser-server

# Start (dev, no build)
pnpm run browser-server:dev

# Debug mode (logs browser and server address)
pnpm run browser-server -- --debug