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

@expo/oclif-dev-cli

v1.26.9-expo

Published

helpers for oclif CLIs

Downloads

4

Vulnerabilities

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

Links

Git

Maintainers

douglowderdouglowderbetoatexpobetoatexpophilplphilplexpo-botexpo-botszdziedzicszdziedzicalanhughesalanhugheskadikramankadikramanradoslawkrzemienradoslawkrzemienaleqsioaleqsiomarklawlormarklawlorgabrieldonadelgabrieldonadelsimeksimekkeith-kurakkeith-kurakfiber-godfiber-godideidebrentvatnebrentvatneevanbaconevanbaconquinlanjquinlanjexpoadminexpoadmintsapetatsapetaexponentexponentwschurmanwschurmanbycedricbycedriclukmccalllukmccalljonsampjonsampprincefleaswallowprincefleaswallowkudochienkudochien

Keywords

oclif

Readme

@oclif/dev-cli

helpers for oclif CLIs

Version CircleCI Appveyor CI Known Vulnerabilities Downloads/week License

Usage

$ npm install -g @oclif/dev-cli
$ oclif-dev COMMAND
running command...
$ oclif-dev (-v|--version|version)
@oclif/dev-cli/1.26.9 linux-x64 node-v14.18.2
$ oclif-dev --help [COMMAND]
USAGE
  $ oclif-dev COMMAND
...

Commands

oclif-dev help [COMMAND]

display help for oclif-dev

USAGE
  $ oclif-dev help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

oclif-dev manifest [PATH]

generates plugin manifest json

USAGE
  $ oclif-dev manifest [PATH]

ARGUMENTS
  PATH  [default: .] path to plugin

See code: src/commands/manifest.ts

oclif-dev pack

packages oclif cli into tarballs

USAGE
  $ oclif-dev pack

OPTIONS
  -r, --root=root        (required) [default: .] path to oclif CLI root
  -t, --targets=targets  comma-separated targets to pack (e.g.: linux-arm,win32-x64)
  --[no-]xz              also build xz

DESCRIPTION
  This can be used to create oclif CLIs that use the system node or that come preloaded with a node binary.

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

oclif-dev pack:deb

pack CLI into debian package

USAGE
  $ oclif-dev pack:deb

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/pack/deb.ts

oclif-dev pack:macos

pack CLI into MacOS .pkg

USAGE
  $ oclif-dev pack:macos

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/pack/macos.ts

oclif-dev pack:win

create windows installer from oclif CLI

USAGE
  $ oclif-dev pack:win

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/pack/win.ts

oclif-dev publish

publish an oclif CLI to S3

USAGE
  $ oclif-dev publish

OPTIONS
  -r, --root=root        (required) [default: .] path to oclif CLI root
  -t, --targets=targets  comma-separated targets to pack (e.g.: linux-arm,win32-x64)

DESCRIPTION
  "aws-sdk" will need to be installed as a devDependency to publish.

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

oclif-dev publish:deb

publish deb package built with pack:deb

USAGE
  $ oclif-dev publish:deb

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/publish/deb.ts

oclif-dev publish:macos

publish macos installers built with pack:macos

USAGE
  $ oclif-dev publish:macos

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/publish/macos.ts

oclif-dev publish:win

publish windows installers built with pack:win

USAGE
  $ oclif-dev publish:win

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/publish/win.ts

oclif-dev readme

adds commands to README.md in current directory

USAGE
  $ oclif-dev readme

OPTIONS
  --dir=dir  (required) [default: docs] output directory for multi docs
  --multi    create a different markdown page for each topic

DESCRIPTION
  The readme must have any of the following tags inside of it for it to be replaced or else it will do nothing:
  # Usage
  <!-- usage -->
  # Commands
  <!-- commands -->

  Customize the code URL prefix by setting oclif.repositoryPrefix in package.json.

See code: src/commands/readme.ts