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

@vived/vived_app_publisher

v3.0.21

Published

This publishes projects to be used as apps in the Vived eco system

Downloads

206

Vulnerabilities

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

Links

Git

Maintainers

mwang_vivmwang_vivkintz_09kintz_09amos.patrickamos.patrickbrochambeaubrochambeau

Keywords

vived

Readme

"@vived/vived_app_publisher"

This publishes projects to be used as apps in the Vived eco system

oclif Version Downloads/week License

Usage

$ npm install -g @vived/vived_app_publisher
$ vap COMMAND
running command...
$ vap (-v|--version|version)
@vived/vived_app_publisher/2.6.11 darwin-x64 node-v12.16.3
$ vap --help [COMMAND]
USAGE
  $ vap COMMAND
...

Commands

vap configure

The "configure" command will take your Vived login information in order to authenticate publishing permissions

USAGE
  $ vap configure

OPTIONS
  -e, --email=email
  -i, --isTesting
  -p, --password=password

vap create

The "create" command will create the initial app and store the data locally to be used later

USAGE
  $ vap create

OPTIONS
  -i, --isTesting

vap help [COMMAND]

display help for vap

USAGE
  $ vap help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

vap publish

The "publish" command will allow you to finalize your app inside of the Vived system

USAGE
  $ vap publish

OPTIONS
  -e, --env=env      [default: prod]
  -i, --isTesting
  -s, --stage=stage  [default: released]

vap configure

The "configure" command will take your Vived login information in order to authenticate publishing permissions

USAGE
  $ vap configure

OPTIONS
  -e, --email=email
  -i, --isTesting
  -p, --password=password

vap create

The "create" command will create the initial app and store the data locally to be used later

USAGE
  $ vap create

OPTIONS
  -i, --isTesting

vap help [COMMAND]

display help for vap

USAGE
  $ vap help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

vap publish

The "publish" command will allow you to finalize your app inside of the Vived system

USAGE
  $ vap publish

OPTIONS
  -e, --env=env      [default: prod]
  -i, --isTesting
  -s, --stage=stage  [default: released]

vap configure

The "configure" command will take your Vived login information in order to authenticate publishing permissions

USAGE
  $ vap configure

OPTIONS
  -e, --email=email
  -i, --isTesting
  -p, --password=password

vap create

The "create" command will create the initial app and store the data locally to be used later

USAGE
  $ vap create

OPTIONS
  -i, --isTesting

vap help [COMMAND]

display help for vap

USAGE
  $ vap help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

vap publish

The "publish" command will allow you to finalize your app inside of the Vived system

USAGE
  $ vap publish

OPTIONS
  -e, --env=env      [default: prod]
  -i, --isTesting
  -s, --stage=stage  [default: prod]