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

@vizualmodel/vmblu-cli

v0.4.2

Published

This folder contains the CLI commands that are available for vmblu.

Readme

CLI for vmblu

This folder contains the CLI commands that are available for vmblu.

Folder layout

vmblu/
  cli/                      # your CLI source
    bin/
      vmblu.js              # discovers and adds commands
    commands/
      init/
      make-app/
      make-test/
      profile/
      migrate/
    templates/
      x.y.z/                # a directory per version x.y.z
        blueprint.schema.json
        blueprint.annex.md
        vizual.schema.json
        profile.schema.json
        system-prompt.project.md
        system-prompt.dev.md
        system-prompt.test.md
    package.json
    README.md
    LICENSE.txt

Add more commands

Create commands/migrate/index.js with the same export shape { command, describe, builder, handler }. The router auto-discovers it.

Dev/test workflow

from vmblu/cli

npm link               # exposes "vmblu" globally
vmblu init my-app --schema 0.8.2
vmblu --help
vmblu init --help

Publish & use

npm publish --access public

Usage

npx @vizualmodel/vmblu-cli init my-app --schema 0.8.2

or, after global install:

vmblu init my-app

Tips

  • Keep templates inside the package and list them in "files" so npx works offline.
  • If you later prefer a richer UX, you can swap the router to commander/yargs without changing your command folders.
  • If your main repo houses both runtime and CLI, publish the CLI from vmblu/cli (separate package.json). This keeps runtime installs lean.
  • This gives you one tidy package for all current and future commands, with zero drift and easy discoverability.