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

viite-cli

v2.2.0

Published

CLI for Viite Business Studio — drive your business back-office from the terminal

Readme

viite-cli

Command-line interface for Viite Business Studio — a business back-office you can drive from your terminal, and which Claude can operate directly through a remote MCP connector.

Install

curl -fsSL https://viite.ai/install | bash

Installs Bun if you don't have it, then the package. Gives you the viite command (and the short alias vt).

Already have Bun? Straight from npm:

npm i -g viite-cli

The npm route needs Bun already on your PATH. npm i -g viite-cli pulls the package fine, but the installed script's shebang runs it with bun, not node — so without Bun the install succeeds and the command then fails with env: bun: No such file or directory. Install Bun first:

curl -fsSL https://bun.sh/install | bash

Why not npm i -g viite?

Because that package does not exist, and cannot:

npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/viite - Not found

npm applies a typosquat filter to new unscoped names and refuses anything too close to an existing one — viite is rejected against vite, write and vfile. That is a deterministic rule, not a name someone else took: nobody can publish viite, us included. The -cli suffix was enough distance, so the package is viite-cli.

A package's name and the commands it installs are independent, so what you type is still viite. Only the one-time install string carries the suffix.

Usage

viite --help

Full command reference and authentication setup: https://developer.viite.ai/cli/

Source file in this repo: apps/developer-website/src/content/docs/apps/cli.md