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

@agentback/files-sdk

v0.13.0

Published

FileStore adapter bridging @agentback/files to files-sdk (one port, 40+ storage backends)

Readme

@agentback/files-sdk

A FileStore adapter that bridges @agentback/files to files-sdk — one port, 40+ storage backends.

@agentback/files-s3 hand-wires the AWS SDK to the FileStore port. This package does the same for files-sdk, whose single Files API already abstracts S3, R2, GCS, Azure Blob, Vercel Blob, Netlify Blobs, MinIO, the local filesystem, and ~30 more behind one interface. Pick a files-sdk adapter, wrap it once, and every AgentBack upload/download recipe (fileField() / fileResponse(...)) runs against that backend unchanged.

Usage

import {FilesSdkFileStore} from '@agentback/files-sdk';
import {s3} from 'files-sdk/s3'; // or files-sdk/r2, /gcs, /azure, /fs, …
import {FILE_STORE} from '@agentback/files';

app
  .bind(FILE_STORE)
  .to(
    new FilesSdkFileStore({adapter: s3({bucket: 'uploads'}), prefix: 'app/'}),
  );

files-sdk is a peer dependency — install it plus the peer deps of the specific adapter you use (e.g. @aws-sdk/client-s3 for s3()); the filesystem adapter needs nothing extra.

How the bridge works

| FileStore | delegates to | bridge detail | | ------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | put(key, body, opts) | files.upload | Buffer is already a Uint8Array (passes through); Readable → Readable.toWeb(). filename rides in metadata (when the backend supports metadata). | | get(key, {range?}) | files.download | body stream ← Readable.fromWeb(sf.stream()); FilesError('NotFound') → FileNotFoundError. A range requires capabilities.rangeRead (throws otherwise). | | stat(key) | files.head | metadata only (no body transfer); maps type→contentType, epoch lastModified→Date; NotFound → FileNotFoundError. | | exists / delete | files.exists / files.delete | delete swallows NotFound to stay idempotent. | | presignedGet / presignedPut | files.url / files.signedUploadUrl | present only when files.capabilities.signedUrl.supported — so S3/R2 stores can presign and a filesystem store reports "unsupported" by omitting the methods. presignedPut returns a SignedUpload (PUT URL, or a size-enforced POST form when opts.maxSize is set). |

The Node ⇄ Web stream conversion is the only real impedance, and it is isolated in toBody() / get() so the same store can run edge-native (Workers/Bun/Deno) later, where the bytes are already Web streams.

Scope

The FileStore port stays minimal: files-sdk's copy/move/list/search, byte-range reads, resumable uploads, and plugins are not projected onto the port. Reach for the underlying files-sdk Files instance directly if you need them.

Testing

The package runs the shared @agentback/files/testing conformance suite against the filesystem adapter — no credentials, no external service — so the bridge is verified in CI exactly like FsFileStore.