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

@buddy-works/drop

v0.1.0

Published

Deploy a folder of static files to a live URL with Buddy Drop - no account needed.

Readme

@buddy-works/drop

Deploy a folder (or .zip) of static files to a live URL with Buddy Drop - no account needed.

npx @buddy-works/drop ./dist --domain my-site.buddy.site
npx @buddy-works/drop ./site.zip --domain my-site.buddy.site

A .zip is unpacked locally before upload - a single top-level folder inside it is flattened away, so a zipped site folder publishes its content at the domain root, exactly like dropping the folder on buddy.works/drop.

The site goes live at https://my-site.buddy.site in about a minute and stays up for 1 hour. The command also prints a claim URL - open it, sign up for a free Buddy account, and the site is yours permanently: the address is kept and the site moves into your own Buddy workspace as a git repository with a configured pipeline, so from then on every git push redeploys it.

Treat the claim URL as sensitive - it expires after 60 minutes and transfers ownership to whoever opens it.

Commands

npx @buddy-works/drop <dir|site.zip> --domain <name.zone>   # deploy at a full address
npx @buddy-works/drop <dir|site.zip> --name <name>          # deploy, first free zone
npx @buddy-works/drop domains <name>                        # zone availability for a name
npx @buddy-works/drop zones                                 # list the free zones

Options

| Flag | Meaning | | --- | --- | | --domain <name.zone> | Full address to publish at, e.g. my-site.buddy.site. | | --name <name> | Subdomain only - the first free zone is picked (or pair with --zone). | | --region <id> | us, eu or asia. Default: detected from the system time zone. | | --json | Machine-readable output (final URLs as one JSON object), no progress lines. | | --api <base> | API base override for one command. |

The API base defaults to https://buddy.works/drop/api; set the BUDDY_DROP_API environment variable to point every command at another Drop deployment (stage, local dev) - --api still wins for a single command.

Limits

Up to 50 files and 100 MB per drop; static files only. The directory should contain an index.html at its root - without one, visitors see a file listing instead of a page.

For AI agents: https://buddy.works/drop/llms.txt