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

pagepocket

v0.4.0

Published

<p align="center">

Readme

PagePocket

PagePocket is a webpage snapshot tool. Given a URL, it loads the page in a headless browser, records network activity, and rewrites remote resources to local files so the page can be viewed offline.

Highlights

  • Captures the final HTML after the page settles.
  • Records fetch/XHR request and response data for offline replay.
  • Downloads static assets (scripts, styles, images, fonts, etc.).
  • Rewrites resource links to local files or inlined Data URLs.
  • Injects a replay script so the snapshot can run without a network connection.

How it works

  1. Page load Uses Puppeteer to launch a headless browser and open the target URL.
  2. Request interception and recording Injects src/preload.ts into the page to wrap fetch and XMLHttpRequest, capturing request/response data in memory. In Node, it also listens to network responses to capture response bodies.
  3. Resource capture and rewrite Parses the HTML with Cheerio, extracts resource URLs (script, link, img, srcset, etc.), downloads them into a local folder, and rewrites HTML references to local paths.
  4. Replay script injection Injects a replay script into the output HTML that swaps remote requests for local or recorded data during offline viewing.

Install

Install globally so the pp CLI is available in your shell:

npm i -g pagepocket

Usage

pp https://example.com
pp https://example.com -o ./snapshots

Output

Snapshots are written to the current directory by default.

Use --output to choose a different directory; filenames still derive from the page title:

  • *.html: offline snapshot page
  • *.requests.json: recorded requests/responses
  • *_files/: downloaded static assets

Example output paths:

  • example.html
  • example.requests.json
  • example_files/
  • snapshots/example.html
  • snapshots/example.requests.json
  • snapshots/example_files/

Configuration

These environment variables control timeouts:

  • PAGEPOCKET_NAV_TIMEOUT_MS: navigation timeout for the initial page load (default: 60000)
  • PAGEPOCKET_PENDING_TIMEOUT_MS: time to wait for tracked fetch/XHR activity to settle (default: 40000)

Notes and limitations

  • PagePocket records fetch/XHR traffic and DOM content, but it does not guarantee capture of every dynamic request if a site continuously streams data.
  • Some sites require authentication or run strict CSP policies; you may need to load the page in a logged-in session or adjust your capture approach.
  • Snapshots are intended for offline viewing and debugging, not for producing a perfect archival copy of every runtime behavior.