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

@anybuild-ai/ab

v0.1.2

Published

Anybuild CLI — sync frontend/UI artifacts with the Anybuild API

Readme

@anybuild-ai/ab

CLI for syncing your Anybuild project files with the cloud.

npm version Node.js License: MIT

Install

npm install -g @anybuild-ai/ab

anybuild --version
anybuild help

Requires Node.js 20+.

Prefer the anybuild command. The package also installs ab, but on many systems that name is already used by ApacheBench.

Update

npm install -g @anybuild-ai/ab@latest
anybuild --version

Quick start

anybuild login https://your-host.example.com
anybuild clone https://your-host.example.com/my-app
cd my-app

# edit files, then:
anybuild status
anybuild push

Sign out when finished (especially on shared machines):

anybuild logout https://your-host.example.com

Workflow

  1. Login to your Anybuild host (stores a session for that host).
  2. Clone an application — creates a ./my-app/ folder by default (git-like). Pass . to use the current directory.
  3. Pull to download the latest remote changes.
  4. Edit tracked project files locally.
  5. Status to see what changed.
  6. Push to upload your changes.

On push conflicts, pull again, resolve locally, then push.

If a push includes deletions, the CLI lists them and asks for confirmation. Pass --yes (or -y) to skip the prompt (required in non-interactive / CI use).

Commands

| Command | Description | | --- | --- | | anybuild login <host-url> | Sign in (prompts for username and password) | | anybuild logout <host-url> | Sign out and remove the local session for that host | | anybuild clone <host-url>/<app> [directory] | Download an application into ./<app>/ (or [directory]; use . for cwd). Options: --force, --debug | | anybuild pull | Download latest changes. Options: --force, --debug | | anybuild status | List local added / modified / deleted files | | anybuild push [paths…] | Upload local changes (optional file paths). Options: --debug, --yes / -y (skip confirm when the push includes deletions) |

Also: anybuild help, anybuild -v / --version.

Clone examples

anybuild clone https://your-host.example.com/my-app
# → ./my-app/

anybuild clone https://your-host.example.com/my-app .
# → current directory

anybuild clone https://your-host.example.com/my-app ./other-folder --force

Configuration

| Location | Purpose | | --- | --- | | ~/.ab/config.json | Your login sessions (credentials for each host) | | .ab/ in the project | Project settings and sync state (no passwords) |

Run project commands (pull, push, status) from inside a cloned application directory.

Security

  • Sessions live in ~/.ab/ with restrictive file permissions on Unix. Do not share or commit that folder.
  • Prefer HTTPS host URLs.
  • On shared machines, run anybuild logout <host-url> when done.
  • Avoid --debug in shared or CI logs.

License

MIT