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

@mikemajara/vcli

v0.1.0

Published

Interactive CLI for managing Vercel projects with batch actions

Readme

vcli

Interactive CLI for managing Vercel projects with batch actions.

Installation

Install from npm (Recommended)

npm install -g vcli

Or using pnpm:

pnpm install -g vcli

Or using yarn:

yarn global add vcli

After installation, you can run vcli from anywhere:

vcli projects --token YOUR_VERCEL_TOKEN

Install from Source

If you want to install from the GitHub repository:

# Clone the repository
git clone https://github.com/miguelalcalde/vercel-enhanced-cli.git
cd vercel-enhanced-cli

# Install dependencies
pnpm install
# or: npm install

# Build the project
pnpm run build
# or: npm run build

# Install globally
pnpm link --global
# or: npm link -g

Local Development

# Clone and install dependencies
git clone https://github.com/miguelalcalde/vercel-enhanced-cli.git
cd vercel-enhanced-cli
pnpm install

# Run in development mode (with watch)
pnpm run dev

# In another terminal, test the CLI
node dist/index.js projects --token YOUR_VERCEL_TOKEN

Usage

Run the CLI:

vcli

Or with a token:

vcli --token YOUR_VERCEL_TOKEN

Or set the token as an environment variable:

export VERCEL_TOKEN=YOUR_VERCEL_TOKEN
vcli

Command Options

  • -t, --token <token> - Vercel API token (or use VERCEL_TOKEN env var)

Features

  • 🔍 Browse Projects: View all your Vercel projects with extended metadata
    • Last updated timestamp
    • Last deployment information
    • Project URLs and domains
  • 👥 Team Management: Switch between personal account and teams
  • 📊 Project Details: View detailed information about each project
  • 🌐 Open URLs: Batch open project URLs in your browser
  • 🗑️ Batch Delete: Select and delete multiple projects with confirmation
  • Lazy Loading: Efficient data fetching with incremental loading
  • 🎨 Interactive UI: Terminal-based selection with keyboard navigation

Authentication

Provide your Vercel API token using one of these methods:

  1. Command-line flag: --token or -t

    vcli --token YOUR_VERCEL_TOKEN
  2. Environment variable: VERCEL_TOKEN

    export VERCEL_TOKEN=YOUR_VERCEL_TOKEN
    vcli
  3. Vercel CLI auth file: The tool can also read from Vercel CLI's auth configuration

Get your token from: https://vercel.com/account/tokens

Requirements

  • Node.js >= 18.0.0

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

License

MIT License - see LICENSE file for details.

Support