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/core

v0.1.0

Published

Shared types, typed error hierarchy, and Logger interface for the @technical-1 Puppeteer suite

Downloads

43

Readme

@technical-1/core

Foundational package for the @technical-1 Puppeteer capability suite. Zero runtime dependencies. Every capability package depends on this for shared contracts.

Exports:

  • Typed error hierarchyPptrKitError (base) and SelectorNotFoundError, NavigationError, TimeoutError, CaptchaError, ProxyError, SessionError. Each carries a retryable flag and a structured context.
  • Logger interface — the dependency-injected logging contract. No implementation lives here (see @technical-1/logger).
  • Shared option shapesLoggerOption, TimeoutOption.
import { SelectorNotFoundError, type Logger } from "@technical-1/core";

Detecting suite errors across packages

This package is published in both ESM and CommonJS form. In mixed ESM/CJS deployments a consumer can end up with two copies of the constructors, so err instanceof PptrKitError is not reliable across package boundaries. Detect and classify suite errors by the stable properties instead — this is the contract @technical-1/retry and other consumers rely on:

function isRetryable(err: unknown): boolean {
  return (
    typeof err === "object" &&
    err !== null &&
    "retryable" in err &&
    (err as { retryable?: unknown }).retryable === true
  );
}

err.name (e.g. "NavigationError") is the cross-realm-safe discriminant for the specific error type; err.retryable is the cross-realm-safe retry signal.