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

@cloudflarebase/hosting

v0.7.0

Published

Apps and functions on Cloudflare Workers for Platforms - static assets and server code in one deploy, one Durable Object orchestrator per project - the hosting primitive behind Cloudflarebase.

Readme

@cloudflarebase/hosting

Apps and functions on Cloudflare Workers for Platforms - static assets and server code in one deploy, served at your subdomain. The hosting primitive behind Cloudflarebase.

One HostingAgent Durable Object per project orchestrates deploys (asset upload sessions, script puts, per-script tags and limits) while the same worker serves every app on a wildcard domain by dispatching the host label straight into the namespace - the script name IS the subdomain, so serving needs zero lookups.

Install

npx @cloudflarebase/cli add hosting

The CLI installs this package, merges template/wrangler-fragment.jsonc into your wrangler.jsonc, prepends the entrypoint re-export, and reruns wrangler types. Workers for Platforms is a paid Cloudflare add-on; the fragment's header documents the manual steps that turn recorded deploys into served apps (dispatch namespace, API token, wildcard route).

What it serves

  • An "app" is one user Worker in the dispatch namespace: a static site, an SSR frontend, backend functions, or all three in one artifact (modules plus an asset manifest).
  • Deploys go through the Cloudflarebase console (bare cloudflarebase init, then cloudflarebase deploy), which resolves the subdomain claim in its control plane and pushes it here - this agent owns no global state.
  • Every script is uploaded with a pid-<projectId> tag (project erase deletes by tag), fixed CPU/subrequest limits applied at dispatch, and injected PROJECT_ID / CLOUDFLAREBASE_URL vars so the SDK works out of the box.

What your Worker serves

Nothing, over HTTP. Every route this agent has - /overview, /apps/* (deploys, secrets), /deploys, the state-sync socket, /internal/* - deploys code, mints subdomains, or writes secrets, and none of them authenticate a caller: they are meant to sit behind a console that already has. Mounted on your own public Worker they answer 404.

Serving deployed apps is unaffected - that runs on your wildcard hostname, ahead of everything else.

Drive deploys from your own code through the HostingAgent Durable Object namespace binding, which no HTTP caller can reach. To serve the routes over HTTP instead, put your own authentication in front and set "EXPOSE_OPERATOR_API": "true" - only on a Worker with no public hostname of its own.

License

Apache-2.0. See NOTICE.