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

ralio

v0.6.1

Published

command-line client for the rallydev API

Downloads

155

Readme

ralio

A usable command-line client for rally.

Installation

$ npm install -g ralio

Configuration

Create a config file in ~/.raliorc.

{
  "username": "USERNAME",
  "password": "PASSWORD",
  "project": "BACKLOG PROJECT NAME",
  "team": "TEAM PROJECT NAME"
}

username and password should be self-explanatory. project and team should contain the name of the Rally projects that correspond to your project backlog and your team. Where I work, we run multiple teams from a common product backlog, hence the different options. If you don't work that way, put the same project name in both.

I suggest you chmod 0600 ~/.raliorc to prevent your password going walkies. In future I'll be stashing credentials in the OS key store. Unfortunately, Rally doesn't use OAuth (or any other kind of API keys), so ralio needs your password to work.

Usage

See the built-in help:

$ ralio --help

  Usage: ralio [options] [command]

  Commands:

    backlog
    Show the product backlog

    sprint [options]
    Show the current team iteration

    show <story>
    Show tasks for an individual story

    open <story>
    Open a story in a web browser

  Options:

    -h, --help     output usage information
    -V, --version  output the version number