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

@handstage/core

v1.0.3

Published

Readme

@handstage/core

Core browser automation engine for Handstage. Manages CDP connections, target routing, page/frame lifecycle, and script injection for reliable browser automation.

Connection ownership

Connection subpath factories own the CDP connection they construct:

  • connectLocal(chrome) from @handstage/core/connect/local — attaches to a launched Chrome pipe and owns the connection.
  • connectWS(ws) from @handstage/core/connect/ws — wraps a browser WebSocket and owns the connection. close() closes the WebSocket.
  • connectTransport(transport) from @handstage/core/connect/transport — wraps and owns a raw CDPTransport.
  • connectSession(session) from @handstage/core/connect/session — wraps and owns an ExternalCDPSession.
  • connectConnection(existingConnection) from @handstage/core/connect/connection — explicit sharing entrypoint. Handstage does NOT close the connection on close(); the caller does.

Wrapping the same transport or session again throws HandstageTransportAlreadyOwnedError.

Context.close() only ever calls Target.disposeBrowserContext (for dedicated contexts). It never tears down the underlying CDP connection — that responsibility lives with Handstage or, for shared connections, the caller.

Default-context attach

Handstage creates instances containing the defaultBrowserContext() by default (which aligns with Puppeteer's puppeteer.connect and puppeteer.launch). Two Handstage clients on the same CDP websocket therefore share the default browser context natively without breaking. If you want isolation, call handstage.createBrowserContext(), which returns an isolated browser context. Targets owned by other browser contexts are resumed/detached at the target router rather than left paused.

To intentionally attach to the shared default context (and accept that other actors may race with you on a shared tab), simply use the default browser context (i.e. handstage.newPage()).

Active page is gone

Contexts no longer auto-create an initial page and there is no context.activePage() / setActivePage() / awaitActivePage(). Track Page references yourself (from newPage() / pages()) and call page.bringToFront() if you want to foreground a tab.

Per-instance logging

Pass logger: to any connection factory and that logger receives every log from that Handstage's contexts / pages / network managers / target-router delegate. Two Handstage instances on a shared connection each receive router-level debug lines via broadcast.