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

@panerelay/sites

v0.11.0

Published

Built-in site catalog for Panerelay browser-backed fetch.

Readme

@panerelay/sites

@panerelay/sites is Panerelay's lockstep catalog of built-in browser-backed fetch adapters. It is one public package for all built-in sites; users do not install one npm package per site.

@panerelay/setup depends on the matching version of this package and installs only the adapters a user explicitly selects:

npx --yes @panerelay/setup add bilibili
npx --yes @panerelay/setup add --all

The package is not a command-line installer. Its public API exposes built-in IDs and their packaged two-file source directories so setup can validate and copy them into protected user storage.

Built-in sites are plain source directories under this package's single TypeScript source root, not nested npm packages or workspaces. Bilibili, Hacker News, and arXiv are laid out directly under packages/sites/src:

  • panerelay.site.ts contains literal site identity and version metadata.
  • Each public command and its typed help metadata live in one matching file under commands/.
  • commands/_shared/ contains only logic reused by multiple commands.
  • client.ts contains optional site-specific API clients and validation helpers.

The package build uses the public @panerelay/site-kit contract to derive dist/adapters/bilibili/panerelay-fetch-adapter.json and bundle adapter.mjs; the source tree has no handwritten manifest, command registry, protocol entrypoint, nested package, or build configuration. External authors use the same layout and toolkit. New built-in sites use this flat directory shape and update only the catalog, artifact tests, and lockstep release inventory.

Run adapter fixture tests with pnpm test. The optional real-site E2E suite runs every migrated command through the installed CLI when the browser is already configured and the required site permissions are available:

PANERELAY_RUN_SITE_E2E=1 pnpm e2e

Run only selected sites with a comma-separated filter:

PANERELAY_RUN_SITE_E2E=1 PANERELAY_E2E_SITES=bilibili pnpm e2e
PANERELAY_RUN_SITE_E2E=1 PANERELAY_E2E_SITES=arxiv,hackernews pnpm e2e

The E2E suite contains representative cases for every migrated OpenCLI site and broader command coverage for selected adapters. Bilibili cases require an authenticated browser session; write commands are intentionally covered without mutating a real account. The suite is skipped unless explicitly enabled because results depend on live sites, browser connectivity, permissions, and login state. An unknown site filter fails immediately instead of silently running no tests.