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

v0.2.1

Published

Headless, provider-agnostic file transfer engine: concurrency, chunking, multipart, retries, and persistence, with no bundled transport or storage provider.

Readme

@upflowi/core

The engine at the center of upflowi: a headless, provider-agnostic file transfer engine. Concurrency, queueing, chunking, retries, progress, pause/resume, cancellation, and resumable persistence — with zero runtime dependencies and no knowledge of any specific transport or storage backend.

@upflowi/core never moves bytes on its own. It orchestrates when and how they move, and delegates the actual HTTP mechanics to an UploadTransport package (@upflowi/transport-fetch, @upflowi/transport-xhr) and — for multipart transfers — to a StorageProvider package (@upflowi/provider-s3, @upflowi/provider-r2, @upflowi/provider-http).

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

const uploader = createUploader({
  concurrency: 3,
  transport: createFetchTransport(),
});

const upload = uploader.add({
  source: {
    fileId: "avatar.png",
    size: file.size,
    read: async () => file,
  },
  options: { url: "https://your-backend.example.com/uploads/avatar.png" },
});

upload.on("progress", (progress) => console.log(`${progress.percent.toFixed(1)}%`));
uploader.start();

What's in this package

  • createUploader(config) — the factory that builds an Uploader: add/addMany, start/pause/resume/cancel, on, and queue introspection.
  • Upload — the per-file handle returned by add()/addMany(): pause(), resume(), cancel(), on(), status.
  • Typed events for both Upload and Uploader: queued, started, progress, paused, resumed, retry, completed, failed, cancelled, allCompleted.
  • Typed errors you can instanceof against: UploadError, NetworkError, HttpError, AbortError, RetryExhaustedError, UploadValidationError, ProviderError.
  • Extension interfaces third-party packages implement: UploadTransport, StorageProvider, UploadStore.
  • Configurable retry/backoff policy (RetryConfig) and an optional per-part checksum abstraction (ChecksumComputer).

@upflowi/core has zero runtime dependencies and no AWS, Cloudflare, XHR, fetch, or IndexedDB code — those live in separate transport/provider/store packages so you only install what you actually use.

You'll also need

At least one transport (moves bytes):

pnpm add @upflowi/transport-fetch   # or @upflowi/transport-xhr

For multipart uploads, a storage provider:

pnpm add @upflowi/provider-s3   # or provider-r2, provider-http

For resumable uploads across a page reload or crash, an UploadStore:

pnpm add @upflowi/store-indexeddb   # or store-memory

Where this runs

Runtime-agnostic by design: no browser or Node.js assumptions are baked in. In practice it's meant to run client-side — a browser tab is the primary target, since the whole point of a presigned-URL provider is bytes flowing straight from the browser to storage, bypassing your backend. @upflowi/transport-fetch also happens to work in Node.js 18+, so the engine can drive a server-to-server transfer too, but that's a secondary use case.

Documentation

See the monorepo README for the full quick start (simple uploads, multipart S3 with presigned URLs, resumable uploads, checksums, events, cancellation, error handling) and AGENTS.md for the architecture behind orchestration vs. scheduling vs. transport vs. provider.

License

ISC