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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@comms/cli

v1.0.3

Published

Comms.dev CLI

Downloads

10

Readme

Comms CLI

Comms CLI is a set of commands using JS/Node to manipulate your Comms.dev stores and Comms Hub shares.

Setup

Install the latest version of @comms/cli

$ npm i -g @comms/cli

Update docker image used for building assets.

$ docker pull commsdev/hub-dev:latest

Configuration

Comms CLI connects to Comms Supervisor and Comms Hub. You need to login there and get your API keys. Then you can manually login to both sites in CLI by running:

$ comms-cli auth:login

You can also skip this step and enter API keys once you'll access features for which the API keys are needed.

Your configuration will be encrypted and stored at ./.comms-cli/.

Troubleshooting

All commands will autodiscover templates in the current working directory. Shares need to be organized in ./$vendor/$type/$name/$name.vue directories/files for the autodiscovery, build and publish processes to work.

Updating comms-cli alias

Sometimes the comms-cli alias fails to be properly set. Update our comms-cli alias manually in our profile.

$ nano ~/.zshrc

alias comms-cli="/usr/local/lib/node_modules/@comms/cli/build/cli-linux"

Or update the symlink directly.

$ ln -sf /usr/local/lib/node_modules/@comms/cli/build/cli-linux /usr/local/bin/comms-cli

Reload the profile (or open another terminal).

$ . ~/.zshrc

Usage

Run comms-cli.

$ comms-cli

Usage: comms-cli [options] [command]

CLI for Comms.dev

Options:
  -V, --version          output the version number
  --vv, --verbose
  --vvv, --debug
  -h, --help             display help for command

Commands:
  auth
  auth:status            Print authentication status for ID, Hub, Supervisor and stores
  auth:login             Login to Comms Hub or Comms Supervisor
  auth:logout            Logout from Comms ID, Hub or Supervisor
  
  store
  store:list [options]   List my stores on Comms Supervisor
  store:status           Check store status
  store:stats            Print store stats
  store:create           Create new development or production store
  
  hub
  hub:list [options]     List my shares on Comms Hub
  hub:bootstrap          Bootstrap files for a new share
  hub:mock [options]     Virtually install local shares to the development store
  hub:serve [options]    Serve local assets to test them on the actual store
  hub:publish [options]  Publish selected shares to Comms Hub
  hub:install            Install published shares to the store
  
  self-update            Pull docker image and try to update npm package when globally installed
  help [command]         display help for command

Help

See Comms Hub kit for more info.