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

bry

v1.1.0

Published

A CLI map assitant

Downloads

8

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

brian.alonsobrian.alonso

Keywords

oclif

Readme

oclif-hello-world

oclif example Hello World CLI

oclif CircleCI GitHub license

Usage

$ npm install -g bry
$ bry COMMAND
running command...
$ bry (--version)
bry/1.1.0 darwin-arm64 node-v18.12.1
$ bry --help [COMMAND]
USAGE
  $ bry COMMAND
...

Commands

bry hello PERSON

Say hello

USAGE
  $ bry hello PERSON -f <value>

ARGUMENTS
  PERSON  Person to say hello to

FLAGS
  -f, --from=<value>  (required) Who is saying hello

DESCRIPTION
  Say hello

EXAMPLES
  $ oex hello friend --from oclif
  hello friend from oclif! (./src/commands/hello/index.ts)

See code: src/commands/hello/index.ts

bry hello world

Say hello world

USAGE
  $ bry hello world

DESCRIPTION
  Say hello world

EXAMPLES
  $ bry hello world
  hello world! (./src/commands/hello/world.ts)

See code: src/commands/hello/world.ts

bry help [COMMANDS]

Display help for bry.

USAGE
  $ bry help [COMMANDS] [-n]

ARGUMENTS
  COMMANDS  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for bry.

See code: @oclif/plugin-help

bry plugins

List installed plugins.

USAGE
  $ bry plugins [--json] [--core]

FLAGS
  --core  Show core plugins.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List installed plugins.

EXAMPLES
  $ bry plugins

See code: @oclif/plugin-plugins

bry plugins:install PLUGIN...

Installs a plugin into the CLI.

USAGE
  $ bry plugins add plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  Plugin to install.

FLAGS
  -f, --force    Run yarn install with force flag.
  -h, --help     Show CLI help.
  -s, --silent   Silences yarn output.
  -v, --verbose  Show verbose yarn output.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Installs a plugin into the CLI.
  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
  $ bry plugins add

EXAMPLES
  $ bry plugins add myplugin 

  $ bry plugins add https://github.com/someuser/someplugin

  $ bry plugins add someuser/someplugin

bry plugins:inspect PLUGIN...

Displays installation properties of a plugin.

USAGE
  $ bry plugins inspect PLUGIN...

ARGUMENTS
  PLUGIN  [default: .] Plugin to inspect.

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Displays installation properties of a plugin.

EXAMPLES
  $ bry plugins inspect myplugin

See code: @oclif/plugin-plugins

bry plugins:install PLUGIN...

Installs a plugin into the CLI.

USAGE
  $ bry plugins install PLUGIN...

ARGUMENTS
  PLUGIN  Plugin to install.

FLAGS
  -f, --force    Run yarn install with force flag.
  -h, --help     Show CLI help.
  -s, --silent   Silences yarn output.
  -v, --verbose  Show verbose yarn output.

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Installs a plugin into the CLI.
  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
  $ bry plugins add

EXAMPLES
  $ bry plugins install myplugin 

  $ bry plugins install https://github.com/someuser/someplugin

  $ bry plugins install someuser/someplugin

See code: @oclif/plugin-plugins

bry plugins:link PLUGIN

Links a plugin into the CLI for development.

USAGE
  $ bry plugins link PLUGIN

ARGUMENTS
  PATH  [default: .] path to plugin

FLAGS
  -h, --help          Show CLI help.
  -v, --verbose
      --[no-]install  Install dependencies after linking the plugin.

DESCRIPTION
  Links a plugin into the CLI for development.
  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.


EXAMPLES
  $ bry plugins link myplugin

See code: @oclif/plugin-plugins

bry plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ bry plugins remove plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ bry plugins unlink
  $ bry plugins remove

EXAMPLES
  $ bry plugins remove myplugin

bry plugins reset

Remove all user-installed and linked plugins.

USAGE
  $ bry plugins reset

See code: @oclif/plugin-plugins

bry plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ bry plugins uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ bry plugins unlink
  $ bry plugins remove

EXAMPLES
  $ bry plugins uninstall myplugin

See code: @oclif/plugin-plugins

bry plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ bry plugins unlink plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ bry plugins unlink
  $ bry plugins remove

EXAMPLES
  $ bry plugins unlink myplugin

bry plugins update

Update installed plugins.

USAGE
  $ bry plugins update [-h] [-v]

FLAGS
  -h, --help     Show CLI help.
  -v, --verbose

DESCRIPTION
  Update installed plugins.

See code: @oclif/plugin-plugins