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

casper-node-launcher

v0.0.6

Published

CLI for run single casper node for test purpose

Downloads

19

Vulnerabilities

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

Links

Git

Maintainers

ryo.kanazawa34ryo.kanazawa34

Keywords

oclif

Readme

casper-node-launcher-js

The npm library for makes easy to run casper node for test purpose.

Only Linux supported currently

oclif Version License

Open in Gitpod

Usage

$ npm install -g casper-node-launcher
$ casper-node-launcher-js COMMAND
running command...
$ casper-node-launcher-js (--version)
casper-node-launcher/0.0.6 linux-x64 node-v16.15.1
$ casper-node-launcher-js --help [COMMAND]
USAGE
  $ casper-node-launcher-js COMMAND
...

Commands

casper-node-launcher-js config [BRANCH] [NETWORKNAME]

Generate config files

USAGE
  $ casper-node-launcher-js config [BRANCH] [NETWORKNAME]

ARGUMENTS
  BRANCH       (v0.9.0|v0.9.3|v0.9.3.1|v0.9.4|v1.0.0|v1.0.1|v1.1.0|v1.1.1|v1.1.2|v1.2.0|v1.2.1|v1.3.0|v1.3.1|v1.3.2|v1.3
               .3|v1.3.4|v1.4.0|v1.4.1|v1.4.2|v1.4.3|v1.4.4|v1.4.5|v1.4.6|v1.4.8|v1.4.9|v1.4.13|v1.4.14|v1.4.15|v1.4.15-
               alt|v1.5.0-rc.1|v1.5.1|dev) [default: v1.5.1] The branch to use
  NETWORKNAME  (casper|casper-test|casper-net-1|casper-example) [default: casper-net-1] The default network name

DESCRIPTION
  Generate config files

See code: dist/commands/config.ts

casper-node-launcher-js download [BRANCH]

Download required assets for running casper node.

USAGE
  $ casper-node-launcher-js download [BRANCH]

ARGUMENTS
  BRANCH  (v0.9.0|v0.9.3|v0.9.3.1|v0.9.4|v1.0.0|v1.0.1|v1.1.0|v1.1.1|v1.1.2|v1.2.0|v1.2.1|v1.3.0|v1.3.1|v1.3.2|v1.3.3|v1
          .3.4|v1.4.0|v1.4.1|v1.4.2|v1.4.3|v1.4.4|v1.4.5|v1.4.6|v1.4.8|v1.4.9|v1.4.13|v1.4.14|v1.4.15|v1.4.15-alt|v1.5.0
          -rc.1|v1.5.1|dev) [default: v1.5.1] The branch to use

DESCRIPTION
  Download required assets for running casper node.

See code: dist/commands/download.ts

casper-node-launcher-js help [COMMANDS]

Display help for casper-node-launcher-js.

USAGE
  $ casper-node-launcher-js 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 casper-node-launcher-js.

See code: @oclif/plugin-help

casper-node-launcher-js node [BRANCH] [NETWORKNAME]

Starts a single Casper node.

USAGE
  $ casper-node-launcher-js node [BRANCH] [NETWORKNAME] [-d]

ARGUMENTS
  BRANCH       (v0.9.0|v0.9.3|v0.9.3.1|v0.9.4|v1.0.0|v1.0.1|v1.1.0|v1.1.1|v1.1.2|v1.2.0|v1.2.1|v1.3.0|v1.3.1|v1.3.2|v1.3
               .3|v1.3.4|v1.4.0|v1.4.1|v1.4.2|v1.4.3|v1.4.4|v1.4.5|v1.4.6|v1.4.8|v1.4.9|v1.4.13|v1.4.14|v1.4.15|v1.4.15-
               alt|v1.5.0-rc.1|v1.5.1|dev) [default: v1.5.1] The branch to use
  NETWORKNAME  (casper|casper-test|casper-net-1|casper-example) [default: casper-net-1] The default network name

FLAGS
  -d, --daemon

DESCRIPTION
  Starts a single Casper node.

See code: dist/commands/node.ts

casper-node-launcher-js plugins

List installed plugins.

USAGE
  $ casper-node-launcher-js plugins [--core]

FLAGS
  --core  Show core plugins.

DESCRIPTION
  List installed plugins.

EXAMPLES
  $ casper-node-launcher-js plugins

See code: @oclif/plugin-plugins

casper-node-launcher-js plugins:install PLUGIN...

Installs a plugin into the CLI.

USAGE
  $ casper-node-launcher-js plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  Plugin to install.

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

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
  $ casper-node-launcher-js plugins add

EXAMPLES
  $ casper-node-launcher-js plugins:install myplugin 

  $ casper-node-launcher-js plugins:install https://github.com/someuser/someplugin

  $ casper-node-launcher-js plugins:install someuser/someplugin

casper-node-launcher-js plugins:inspect PLUGIN...

Displays installation properties of a plugin.

USAGE
  $ casper-node-launcher-js 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
  $ casper-node-launcher-js plugins:inspect myplugin

casper-node-launcher-js plugins:install PLUGIN...

Installs a plugin into the CLI.

USAGE
  $ casper-node-launcher-js plugins:install PLUGIN...

ARGUMENTS
  PLUGIN  Plugin to install.

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

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
  $ casper-node-launcher-js plugins add

EXAMPLES
  $ casper-node-launcher-js plugins:install myplugin 

  $ casper-node-launcher-js plugins:install https://github.com/someuser/someplugin

  $ casper-node-launcher-js plugins:install someuser/someplugin

casper-node-launcher-js plugins:link PLUGIN

Links a plugin into the CLI for development.

USAGE
  $ casper-node-launcher-js plugins:link PLUGIN

ARGUMENTS
  PATH  [default: .] path to plugin

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

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
  $ casper-node-launcher-js plugins:link myplugin

casper-node-launcher-js plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ casper-node-launcher-js plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

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

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ casper-node-launcher-js plugins unlink
  $ casper-node-launcher-js plugins remove

casper-node-launcher-js plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ casper-node-launcher-js plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

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

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ casper-node-launcher-js plugins unlink
  $ casper-node-launcher-js plugins remove

casper-node-launcher-js plugins:uninstall PLUGIN...

Removes a plugin from the CLI.

USAGE
  $ casper-node-launcher-js plugins:uninstall PLUGIN...

ARGUMENTS
  PLUGIN  plugin to uninstall

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

DESCRIPTION
  Removes a plugin from the CLI.

ALIASES
  $ casper-node-launcher-js plugins unlink
  $ casper-node-launcher-js plugins remove

casper-node-launcher-js plugins update

Update installed plugins.

USAGE
  $ casper-node-launcher-js plugins update [-h] [-v]

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

DESCRIPTION
  Update installed plugins.

casper-node-launcher-js stop [BRANCH] [NETWORKNAME]

Generate config files

USAGE
  $ casper-node-launcher-js stop [BRANCH] [NETWORKNAME]

ARGUMENTS
  BRANCH       (v0.9.0|v0.9.3|v0.9.3.1|v0.9.4|v1.0.0|v1.0.1|v1.1.0|v1.1.1|v1.1.2|v1.2.0|v1.2.1|v1.3.0|v1.3.1|v1.3.2|v1.3
               .3|v1.3.4|v1.4.0|v1.4.1|v1.4.2|v1.4.3|v1.4.4|v1.4.5|v1.4.6|v1.4.8|v1.4.9|v1.4.13|v1.4.14|v1.4.15|v1.4.15-
               alt|v1.5.0-rc.1|v1.5.1|dev) [default: v1.5.1] The branch to use
  NETWORKNAME  (casper|casper-test|casper-net-1|casper-example) [default: casper-net-1] The default network name

DESCRIPTION
  Generate config files

See code: dist/commands/stop.ts