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

@upflowi/provider-s3

v0.2.1

Published

upflowi storage provider for AWS S3 multipart uploads, driven entirely by presigned URLs your own backend generates. Never receives AWS credentials.

Readme

@upflowi/provider-s3

A StorageProvider for upflowi that drives AWS S3 multipart uploads entirely through presigned URLs your own backend generates. This package never receives or stores AWS credentials — it only calls the getPresignedUrl callback you provide.

pnpm add @upflowi/core @upflowi/transport-fetch @upflowi/provider-s3
import { createUploader } from "@upflowi/core";
import { createFetchTransport } from "@upflowi/transport-fetch";
import { createS3Provider } from "@upflowi/provider-s3";

const provider = createS3Provider({
  getPresignedUrl: (operation) => backendClient.getS3PresignedUrl(operation),
});

const uploader = createUploader({
  concurrency: 3,
  chunkSize: 8 * 1024 * 1024, // 8 MiB parts
  transport: createFetchTransport(),
  provider,
});

How it works

createS3Provider calls your getPresignedUrl callback once per S3 operation the multipart lifecycle needs (create, uploadPart, complete, abort, listParts) and does the rest — signing, XML parsing, and mapping the result onto StorageProvider. Your backend's only job is to sign a CreateMultipartUploadCommand/UploadPartCommand/CompleteMultipartUploadCommand/AbortMultipartUploadCommand/ListPartsCommand and return the URL — it never needs the AWS SDK client itself to touch the request body.

listParts support (via StorageProvider.resume) lets a paired UploadStore (@upflowi/store-indexeddb or @upflowi/store-memory) resume a multipart upload after a reload or crash without re-transferring parts S3 already has.

Checksums

Supports "SHA-256", "CRC32", and "MD5" via @upflowi/core's optional checksum config — compute() must return base64. SHA-256/CRC32 use S3's additional-checksums feature (x-amz-checksum-*); MD5 uses the older Content-MD5 header. See the monorepo README's checksum table for the exact wiring, including the ChecksumAlgorithm your backend must pass to CreateMultipartUploadCommand.

Peer dependency

Requires @upflowi/core as a peer dependency — install both.

Documentation

See the monorepo README for the full multipart S3 example (client + backend) and AGENTS.md for the architecture.

License

ISC