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

@rezakalfane/mynewcli

v1.0.0

Published

My new CLI

Downloads

2

Vulnerabilities

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

Links

Git

Maintainers

rezakalfanerezakalfane

Keywords

oclif

Readme

mynewcli

My new CLI

oclif Version Downloads/week License

Usage

$ npm install -g @rezakalfane/mynewcli
$ mynewcli COMMAND
running command...
$ mynewcli (-v|--version|version)
@rezakalfane/mynewcli/1.0.0 darwin-x64 node-v14.15.0
$ mynewcli --help [COMMAND]
USAGE
  $ mynewcli COMMAND
...

Commands

mynewcli hello [FILE]

describe the command here

USAGE
  $ mynewcli hello [FILE]

OPTIONS
  -f, --force
  -h, --help       show CLI help
  -n, --name=name  name to print

EXAMPLE
  $ mynewcli hello
  hello world from ./src/hello.ts!

See code: src/commands/hello.ts

mynewcli help [COMMAND]

display help for mynewcli

USAGE
  $ mynewcli help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

mynewcli plugins

list installed plugins

USAGE
  $ mynewcli plugins

OPTIONS
  --core  show core plugins

EXAMPLE
  $ mynewcli plugins

See code: @oclif/plugin-plugins

mynewcli plugins:install PLUGIN...

installs a plugin into the CLI

USAGE
  $ mynewcli 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
  $ mynewcli plugins:add

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

See code: @oclif/plugin-plugins

mynewcli plugins:link PLUGIN

links a plugin into the CLI for development

USAGE
  $ mynewcli 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
  $ mynewcli plugins:link myplugin

See code: @oclif/plugin-plugins

mynewcli plugins:uninstall PLUGIN...

removes a plugin from the CLI

USAGE
  $ mynewcli plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

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

ALIASES
  $ mynewcli plugins:unlink
  $ mynewcli plugins:remove

See code: @oclif/plugin-plugins

mynewcli plugins:update

update installed plugins

USAGE
  $ mynewcli plugins:update

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

See code: @oclif/plugin-plugins

mynewcli world [FILE]

describe the command here

USAGE
  $ mynewcli world [FILE]

OPTIONS
  -f, --force
  -h, --help       show CLI help
  -n, --name=name  name to print

EXAMPLE
  $ mynewcli world
  hello world from ./src/world.ts!

See code: src/commands/world.ts