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

oclif-template

v0.0.1

Published

oclif multi command, space separated cli

Downloads

4

Readme

oclif-template

oclif Version Downloads/week License

Development

Starting a development session is easy, just run yarn nodemon once all dependencies are installed. You can create an alias to the absolute path to ./bin/run so you can easily run the CLI in development to test. In Linux, if you use bash, you can add to the end of ~/.bashrc the following line:

alias YOUR_CLI_NAME-test="ABSOLUTE_PATH_TO_YOUR_CLI_FOLDER/bin/run"

After restarting the active terminals you'll be able to run YOUR_CLI_NAME-test and you'll be running the dev version of your CLI.

In MacOS you can add to the end of ~/.bash_profile (if you use bash) the same line presented above - maybe you'll have to restart the computer for the new alias to take effect.

Usage

$ npm install -g oclif-template
$ cli COMMAND
running command...
$ cli (-v|--version|version)
oclif-template/0.0.1 linux-x64 node-v12.13.0
$ cli --help [COMMAND]
USAGE
  $ cli COMMAND
...

Commands

cli help [COMMAND]

display help for cli

USAGE
  $ cli help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

cli ls

List local files

USAGE
  $ cli ls

EXAMPLE
  cli ls

See code: src/commands/ls.ts

cli say:bye

Say bye

USAGE
  $ cli say:bye

EXAMPLE
  cli say bye

See code: src/commands/say/bye.ts

cli say:hello [FILE]

Say hello

USAGE
  $ cli say:hello [FILE]

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

EXAMPLES
  cli say hello
  cli say hello --name="tiago"
  cli say hello -n tiago
  cli say hello --force --file asdf.txt

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

cli update [CHANNEL]

update the cli CLI

USAGE
  $ cli update [CHANNEL]

See code: @oclif/plugin-update