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

@voyantcloud/cli

v0.0.2

Published

Voyant CLI - Simplify local development and deployment

Readme

Voyant CLI

With the Voyant command line interface, you can:

  • Initialize and link projects to your Voyant workspace
  • Authenticate your local development environment
  • Monitor deployment status across environments
  • Manage multiple workspaces and projects

Before you begin

Install the latest version of Node.js (v18 or higher) and a package manager of your choice.

Installation

npm install -g @voyantcloud/cli

Or with other package managers:

pnpm add -g @voyantcloud/cli
yarn global add @voyantcloud/cli

Quick Start

# Login to your Voyant account
voyant login

# Initialize your project
voyant init

# Start local dev server, then authenticate localhost
npm run dev
voyant dev

Commands

Authentication

| Command | Description | |---------|-------------| | voyant login | Authenticate with Voyant via browser | | voyant logout | Clear stored credentials | | voyant whoami | Show current user and workspaces |

Project Setup

| Command | Description | |---------|-------------| | voyant init | Initialize a project (creates voyant.json) | | voyant link | Link to a different project | | voyant unlink | Remove project configuration |

Development

| Command | Description | |---------|-------------| | voyant dev | Authenticate localhost for development | | voyant dev --payload | Also authenticate Payload CMS admin | | voyant dev --token-only | Output token only (for CI/scripts) |

Utilities

| Command | Description | |---------|-------------| | voyant status | Show deployment status | | voyant open | Open project in dashboard | | voyant config | Display current configuration | | voyant workspaces | List available workspaces | | voyant projects | List projects in a workspace |

Configuration

Running voyant init creates a voyant.json file in your project root:

{
  "$schema": "https://voyantcloud.com/schemas/voyant.json",
  "workspaceId": "wksp_abc123",
  "projectId": "proj_xyz789",
  "devUrl": "http://localhost:3000",
  "framework": "nextjs"
}

This file is safe to commit — it contains no secrets.

Supported Frameworks

The CLI auto-detects: Next.js, Remix, Nuxt, Astro, Cloudflare Workers, and Static Sites.

Debug Mode

For troubleshooting, enable debug output:

voyant --debug <command>

Help

If you encounter issues or have feedback:

Publishing

For maintainers preparing a release to the public npm registry via pnpm:

  • Ensure a clean working tree and run pnpm install
  • Validate locally with pnpm test (and pnpm lint / pnpm typecheck if available)
  • Build the distributable with pnpm build (also runs automatically on pnpm publish)
  • Publish with pnpm publish --access public --tag latest

License

MIT