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

@echo./cli

v0.2.12

Published

echo everything

Downloads

58

Readme

@echo./cli

echo everything

oclif Version CircleCI Downloads/week License

Usage

$ npm install -g @echo./cli
$ echo. COMMAND
running command...
$ echo. (-v|--version|version)
@echo./cli/0.2.11 linux-x64 node-v14.15.1
$ echo. --help [COMMAND]
USAGE
  $ echo. COMMAND
...

Commands

echo. conf [KEY] [VALUE]

manage configuration

USAGE
  $ echo. conf [KEY] [VALUE]

ARGUMENTS
  KEY    key of the config
  VALUE  value of the config

OPTIONS
  -d, --cwd=cwd          config file location
  -d, --delete           delete?
  -h, --help             show CLI help
  -k, --key=key          key of the config
  -n, --name=name        config file name
  -p, --project=project  project name
  -v, --value=value      value of the config

See code: conf-cli

echo. help [COMMAND]

display help for echo.

USAGE
  $ echo. help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

echo. mp:init

USAGE
  $ echo. mp:init

OPTIONS
  -c, --custom                     custom some handle logic after created project
  -d, --develop=develop            [default: yarn dev] starting projects command such as yarn dev
  -f, --firstCommit=firstCommit    [default: first commit] your first commit message
  -g, --git                        comfirm if you need init git to your project
  -h, --hosting=hosting            (required) [default: github.com] git hosting
  -i, --initialize=initialize      [default: yarn install] project initialize command such as yarn install
  -n, --name=name                  (required) [default: echo-helloworld] project name
  -p, --preset=preset              (required) [default: echoings/stencil.] git repo
  -r, --remoteOrigin=remoteOrigin  your remote origin
  -s, --stencil=stencil            (required) [default: web-vue-vuetify] git branch or tag
  -t, --type=type                  [default: new] project type

echo. plugins

list installed plugins

USAGE
  $ echo. plugins

OPTIONS
  --core  show core plugins

EXAMPLE
  $ echo. plugins

See code: @oclif/plugin-plugins

echo. plugins:install PLUGIN...

installs a plugin into the CLI

USAGE
  $ echo. plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  plugin to install

OPTIONS
  -f, --force    yarn install with force flag
  -h, --help     show CLI help
  -v, --verbose

DESCRIPTION
  Can be installed from npm or a git url.

  Installation of a user-installed plugin will override a core plugin.

  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command 
  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in 
  the CLI without the need to patch and update the whole CLI.

ALIASES
  $ echo. plugins:add

EXAMPLES
  $ echo. plugins:install myplugin 
  $ echo. plugins:install https://github.com/someuser/someplugin
  $ echo. plugins:install someuser/someplugin

See code: @oclif/plugin-plugins

echo. plugins:link PLUGIN

links a plugin into the CLI for development

USAGE
  $ echo. plugins:link PLUGIN

ARGUMENTS
  PATH  [default: .] path to plugin

OPTIONS
  -h, --help     show CLI help
  -v, --verbose

DESCRIPTION
  Installation of a linked plugin will override a user-installed or core plugin.

  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello' 
  command will override the user-installed or core plugin implementation. This is useful for development work.

EXAMPLE
  $ echo. plugins:link myplugin

See code: @oclif/plugin-plugins

echo. plugins:uninstall PLUGIN...

removes a plugin from the CLI

USAGE
  $ echo. plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

OPTIONS
  -h, --help     show CLI help
  -v, --verbose

ALIASES
  $ echo. plugins:unlink
  $ echo. plugins:remove

See code: @oclif/plugin-plugins

echo. plugins:update

update installed plugins

USAGE
  $ echo. plugins:update

OPTIONS
  -h, --help     show CLI help
  -v, --verbose

See code: @oclif/plugin-plugins

echo. utils:init

Initialize new project by a pre template

USAGE
  $ echo. utils:init

OPTIONS
  -c, --custom                     custom some handle logic after created project
  -d, --develop=develop            [default: yarn dev] starting projects command such as yarn dev
  -f, --firstCommit=firstCommit    [default: first commit] your first commit message
  -g, --git                        comfirm if you need init git to your project
  -h, --hosting=hosting            (required) [default: github.com] git hosting
  -i, --initialize=initialize      [default: yarn install] project initialize command such as yarn install
  -n, --name=name                  (required) [default: echo-helloworld] project name
  -p, --preset=preset              (required) [default: echoings/stencil.] git repo
  -r, --remoteOrigin=remoteOrigin  your remote origin
  -s, --stencil=stencil            (required) [default: web-vue-vuetify] git branch or tag
  -t, --type=type                  [default: new] project type

echo. web:init

USAGE
  $ echo. web:init

OPTIONS
  -c, --custom                     custom some handle logic after created project
  -d, --develop=develop            [default: yarn dev] starting projects command such as yarn dev
  -f, --firstCommit=firstCommit    [default: first commit] your first commit message
  -g, --git                        comfirm if you need init git to your project
  -h, --hosting=hosting            (required) [default: github.com] git hosting
  -i, --initialize=initialize      [default: yarn install] project initialize command such as yarn install
  -n, --name=name                  (required) [default: echo-helloworld] project name
  -p, --preset=preset              (required) [default: echoings/stencil.] git repo
  -r, --remoteOrigin=remoteOrigin  your remote origin
  -s, --stencil=stencil            (required) [default: web-vue-vuetify] git branch or tag
  -t, --type=type                  [default: new] project type