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

rsi.cli

v0.4.6

Published

The swiss army knife for RSI related tasks.

Downloads

104

Readme

RSI (RESTful Service Interface) command line interface

Build Status npm version

RSI.cli

The swiss army knife for RSI related tasks.

This project supports the RESTful Service Interface as published under https://www.w3.org/Submission/2016/01/.

The framework proposes a slightly out-of-date JSON schema for service definitions, so this module uses the service schema published under https://github.com/wzr1337/rsi.schema

Installation

To install the cli globally run the following command:

$ npm i -g rsi.cli

Usage

Usage: rsi <commands...> [options...]

options

| option | alias | meaning | | --------------- | ----- |-------------------------------------------------------- | | --version | -v | Print the version | | --help | -h | Print this usage guide |

commands

| command | what it does | | ----------------------------- | --------------------------------------------------------------- | | service | operate on service level | | bundle | operate on service bundle level |

service

Usage:

$ rsi service

prints you a list of available commands on service level.

commands

| command | what it does | | ----------------------------- | --------------------------------------------------------------- | | document | render HTML documentation based on the schema | | init | initialize a new repository | | release | prepare service for release | | render | render UML from schema | | markdown | render markdown documentation based on the schema | | validate | validate a schema |

bundle

Usage:

$ rsi bundle

prints you a list of available commands on service level.

commands

| command | what it does | | ----------------------------- | --------------------------------------------------------------- | | document | render HTML documentation based on the schemas in the bundle | | render | render bundle UML | | markdown | render markdown documentation based for bundle | | validate | validate a schemas in bundle |

document

Usage:

$ rsi <service||bundle> document --sourceFolder <pathToServiceFolder> --output <pathToOutputFolder>

or

$ rsi <service||bundle> document -s <pathToServiceFolder> -o <pathToOutputFolder>

Renders a set of HTML documents out of the schema.json file contained in <pathToServiceFolder> into <pathToOutputFolder>.

RSI.doc.demo

options

| option | alias | meaning | | --------------- | ----- | ------------------------------------------------------- | | --sourceFolder | -s | the root folder of the project definition repository | | --outputFolder | -o | the output folder for the generated documentation | | --watch | -w | watch the source folder for changes |

init

Usage:

$ rsi service init

initializes an empty service definition repository with the following sturcture:

├── CHANGELOG.md
├── README.md
├── package.json
└── src
    └── schema.json

After you initialized the repository, you can start editing the src/schema.json file. Please be aware that it must comply with the schema definition found under https://github.com/wzr1337/rsi.schema/blob/master/doc/schema.spec.md

RSI.cli

options

init does not support any options

release

Usage:

$ rsi service release

releases a service definition in the desired way:

options

init does not support any options

render

Usage:

$ rsi <service||bundle> render --sourceFolder <pathToServiceFolder> --output <pathToOutputFolder>

or

$ rsi <service||bundle> render -s <pathToServiceFolder> -o <pathToOutputFolder>

Renders a class diagram (plantuml) out of the schema.json file contained in <pathToServiceFolder> into <pathToOutputFolder>.

options

| option | alias | meaning | | --------------- | ----- | ------------------------------------------------------- | | --sourceFolder | -s | the root folder of the project definition repository | | --outputFolder | -o | the output folder for the generated diagram | | --watch | -w | watch the source folder for changes |

markdown

Usage:

$ rsi <service||bundle> markdown --sourceFolder <pathToServiceFolder> --output <pathToOutputFolder>

or

$ rsi <service||bundle> markdown -s <pathToServiceFolder> -o <pathToOutputFolder>

Renders a markdown document out of the schema.json file contained in <pathToServiceFolder> into <pathToOutputFolder>.

options

| option | alias | meaning | | --------------- | ----- | ------------------------------------------------------- | | --sourceFolder | -s | the root folder of the project definition repository | | --outputFolder | -o | the output folder for the generated documentation | | --watch | -w | watch the source folder for changes |

validate

Usage:

$ rsi <service||bundle> validate --sourceFolder <pathToServiceFolder>

or

$ rsi <service||bundle> validate -s <pathToServiceFolder>

Validates schema.json file contained in <pathToServiceFolder>.

options

| option | alias | meaning | | --------------- | ----- | ------------------------------------------------------- | | --sourceFolder | -s | the root folder of the project definition repository | | --watch | -w | watch the source folder for changes |