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

@mieweb/cloud-adapters

v0.2.1

Published

Off-Cloudflare adapters for the @mieweb/cloud contracts, plus the Node host harness that runs the unchanged worker. `.`/`./local`: D1→SQLite, R2→filesystem, KV→in-memory, Queues→in-process, Durable Objects→in-process, Vectorize→sqlite-vec. `./os` (os.miew

Readme

@mieweb/cloud-adapters

Off-Cloudflare implementations of the @mieweb/cloud contracts, plus the Node host harness that runs the unchanged worker handler. The mieweb CLI drives this package for the local and mieweb targets; apps rarely import it directly.

| Subpath | Target | Backends | | --- | --- | --- | | . / ./local | local — zero external services | D1→SQLite (better-sqlite3, FTS5 kept), R2→filesystem, KV→in-memory, Queues→in-process, Durable Objects→in-process registry, Vectorize→sqlite-vec, AI→Ollama when configured | | ./os | mieweb — os.mieweb.org / self-hosted | D1→libSQL/sqld, Vectorize→libSQL native vectors, R2→S3-compatible (MinIO, SeaweedFS, AWS), KV+Queues→Valkey/Redis; AI + Durable Objects reused from local | | ./host | both | startLocalHost({ config }) — imports the worker, builds Env, serves fetch/queue/scheduled | | ./migrate | both | applyMigrations for wrangler-style D1 migrations |

Importing ./os registers its drivers into the shared registry (registerDriver(name, factory)), so createCloudEnv dispatches by the driver field in mieweb.jsonc with no core changes. Surfaces a target can't provide throw an explicit UnsupportedBindingError rather than failing quietly.

Backend SDKs are optional peers

Install only what your target uses; each adapter loads its SDK lazily and throws a clear "install X" error if it's missing.

# local target
pnpm add -D better-sqlite3 sqlite-vec

# mieweb target
pnpm add -D @libsql/client @aws-sdk/client-s3 ioredis

Configure the mieweb target

Copy the targets.mieweb block from mieweb.sample.jsonc into the app's mieweb.jsonc, then mieweb --target mieweb dev.

Develop / test against live infra

pnpm --filter @mieweb/cloud-adapters infra:up    # libSQL + MinIO + Valkey (docker compose)
pnpm --filter @mieweb/cloud-adapters test        # local + os conformance suites
pnpm --filter @mieweb/cloud-adapters infra:down  # tear down (-v removes volumes)

Both suites self-skip whatever isn't installed or reachable, so pnpm -r test stays green without Docker or native builds.

Status: 0.x — the API may change between minor versions.

Full documentation lives in the repository README.