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

@technical-1/tabs

v1.0.0

Published

Coordinate popups and new tabs: race a click against 'targetcreated' and return the settled Page with timeout + cleanup

Readme

@technical-1/tabs

Coordinate popups and new tabs within one browser. Race a user gesture (a click that calls window.open, or a target="_blank" navigation) against the browser's 'targetcreated' event and get back the settled Page — with a typed timeout and guaranteed listener cleanup. You inject the Browser.

This is not process pooling: @technical-1/launcher's BrowserPool pools whole browser processes; tabs waits for a new page inside a browser you already have.

import { waitForNewPage, waitForPageMatching } from "@technical-1/tabs";

// Wait for whatever tab the click opens:
const popup = await waitForNewPage(browser, () => page.click("a[target=_blank]"));

// Wait for a specific popup by URL:
const checkout = await waitForPageMatching(
  browser,
  () => page.click("#pay"),
  (url) => url.startsWith("https://checkout.example.com/"),
  { timeout: 15_000 },
);

Behaviour

  • The 'targetcreated' listener is attached before your trigger runs, so a popup that opens synchronously during the click is never missed.
  • Only page-type targets are considered (service_worker / background_page targets are ignored). waitForPageMatching further filters by your URL predicate; a predicate or target.url() that throws just skips that target.
  • On success, timeout, or failure the listener is detached and the timer cleared — nothing leaks.

Errors

  • Timeout (no matching page in timeout ms, default 30000) → a @technical-1/core TimeoutError with retryable: true and context: { timeout }.
  • Trigger threw or target page could not be resolved → a @technical-1/core PptrKitError with retryable: false, carrying the original cause.

Requirements

puppeteer-core is a peer dependency (>=22 <25) — install it in your project. This package does not launch or close browsers.