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

waker-cli

v0.0.6

Published

Waker-cli is command tool form to manage waker servers

Downloads

1

Readme

waker-cli

This is a command line tool to create and manage waker servers.

##Install To install latest version of waker-cli, run following command:

npm install -g waker-cli

##Commands List of waker-cli commands can be seen by running:

waker --help

###init The command is used to create new waker server.

usage

waker init [options]

options

-p --path <path>          server creation path
-v --version <version>    version of waker to use

###run The command is used to run waker server.

usage

waker run [options]

options

-b --background            run as background
-e --environment <name>    environment to run server

###add The command is used to create new modules/entities in waker server.

usage

waker add <type> [options]

types

module    waker module
entity    system entity

options

-n --name <name>      name of module or entity (required)
-m --module <name>    name of module to add entity in (required if type is entity)

###enable The command is used to enable plugins/helpers in waker server.

usage

waker enable <type> [options]

types

helper    waker helper
plugin    waker integrated hapi plugin

options

-n --name <name>    name of helper/plugin to enable (required)

###disable The command is used to disable plugins/helpers in waker server.

usage

waker disable <type> [options]

types

helper    waker helper
plugin    waker integrated hapi plugin

options

-n --name <name>    name of helper/plugin to disable (required)

###config The command is used to config plugins/helpers in waker server.

usage

waker config <type> [options]

types

helper    waker helper
plugin    waker integrated hapi plugin

options

-n --name <name>    name of helper/plugin to disable (required)

###show The command is used to show info about waker server.

usage

waker show <type> [options]

types

version     version of waker of server
status      list of plugins and helpers with their enable/disable status and version
modules     list of waker modules and their dependencies
entities    list of waker entities

options

-m --module <name>    name of module to see its entities (acceptable if type is entities)

###test The command is used to run tests

usage

waker test [options]

options

-m --module <name>    name of module to run its tests
-t --type <type>      type of tests to run. Acceptable types are "unit" and "functional"