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

@wranglr/cli

v1.0.8

Published

CLI tool for Wranglr.co.za - Deploy static sites to the Edge

Readme

@wranglr/cli

The official command-line interface for Wranglr.co.za.

Designed for developers and modern agencies, the Wranglr CLI provides a frictionless local-to-edge deployment pipeline. With a single command, you can deploy static assets, single-page applications, and compiled frameworks directly to Cloudflare's global edge network through your Wranglr account.


📦 Installation

Install the package globally via npm to access the wranglr command from anywhere on your system:

npm install -g @wranglr/cli

🔑 Authentication

To interact with the platform, you must first authenticate the CLI with your Wranglr account.

wranglr login

  1. Generate a personal API Token from your Dashboard Settings.
  2. Run the login command in your terminal:
    wranglr login
  3. Paste the token when prompted. The CLI explicitly encrypts and stores this session locally.

wranglr whoami

Verify your current authentication status and active user profile:

wranglr whoami

wranglr logout

Removes your local session and API token.

wranglr logout

🚀 Deployment Workflows

The CLI handles automatic compression, diffing, and uploading of static assets natively to the Wranglr Edge Network (backed by R2).

wranglr list

View a comprehensive list of all your active projects, their current deployment status, and their assigned unique origins or custom domains.

wranglr list

wranglr deploy

The core command to ship code. You can target a specific build folder or a pre-packaged .zip file. The CLI recursively detects files, assigns correct MIME types, and synchronizes them to your store ID.

Deploying a Directory (e.g., React/Vue/Vite outputs):

# Navigate to your compiled output directory
cd dist
# Deploy linking to your specific site hostname or ID
wranglr deploy --site my-site.com

Deploying an Archive: Have a legacy client providing .zip drops? Just point the CLI to it:

wranglr deploy ./website.zip --site my-site.com

Flags & Options:

| Flag | Description | Mandatory | |---|---|---| | --site | The registered hostname or absolute Site ID you wish to deploy assets to. | Yes |

Note: Deployment will immediately invalidate cache for the associated Edge assets, making updates globally live within seconds.


🛠 Advanced Usage & CI/CD

When executing deployments in automated environments (like GitHub Actions), ensure the WRANGLR_API_TOKEN environment variable is injected into the runner. The CLI will gracefully bypass interactive authentication prompts if this token is universally present.

Help & Support

To view the in-terminal help manual for any command, utilize the --help flag:

wranglr --help
wranglr deploy --help

For platform issues, billing, or feature requests, contact [email protected] or use the chat widget inside the merchant dashboard.