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

@beezping/screenshot-storage

v0.2.1

Published

Screenshot storage for Beezping — Cloudflare Images, any S3-compatible bucket, your database (Drizzle: PostgreSQL, Turso/libSQL), the local filesystem, memory, or your own backend

Readme

npm version Docs TypeScript

@beezping/screenshot-storage

Screenshot storage for the Beezping stores: upload screenshots to Cloudflare R2, AWS S3 or any S3-compatible bucket, Cloudflare Images, your database through Drizzle, or your disk, and keep only their URL in the feedback. No AWS SDK and no runtime dependency: it runs on Node, Bun, Deno and edge workers.

Documentation

Install

npm install @beezping/screenshot-storage

Node ≥ 20, or any runtime with the Fetch and Web Crypto APIs (the /filesystem entry needs Node). drizzle-orm is an optional peer, only for the /drizzle-pg and /drizzle-libsql entries.

Quick start

import { createScreenshotStorage } from "@beezping/screenshot-storage";
import { createS3ObjectStore } from "@beezping/screenshot-storage/s3";

const screenshotStorage = createScreenshotStorage(
  createS3ObjectStore({
    endpoint: `https://${process.env.R2_ACCOUNT_ID}.r2.cloudflarestorage.com`,
    bucket: "beezping-screenshots",
    accessKeyId: process.env.R2_ACCESS_KEY_ID!,
    secretAccessKey: process.env.R2_SECRET_ACCESS_KEY!,
    publicBaseUrl: "https://screenshots.example.com",
  }),
);

// Prisma: createBeezpingHandler({ prisma, screenshotStorage })
// Drizzle: createPgBeezpingStore(db, { screenshotStorage })

Every upload gets a fresh random key, delete only removes objects it created, and backends without a public URL are served from your app by createScreenshotServeHandler.

Documentation

Every backend, serving screenshots from your app, least-privilege credentials, options, delete semantics and custom backends: github.com/guidomodarelli/beezping/docs/adapters/screenshot-storage.

License

MIT