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

tftools

v2.1.0

Published

Tools for getting extra TFS/VSTS/ADO info

Downloads

15

Readme

tftools

Build Status

Installation

from a new directory npm install tftools

or for the global CLI npm install -g tftools

including the reference const ADOToolsModule = require(“tftools”)

Examples

Using the CLI

Options

$ tftools velocities -h                                                                                                                                          
Usage: velocities [options]

get  velocities for all teams in a project

Options:
  --project <name>            the ADO project analyze (default: "<ENTER A PROJECT NAME>")
  -c, --count <count>         the number of team velocities to collect
  -f --file_name <name>       the name of the output file. Defaults to velocities.csv (default: "velocities.csv")
  --exclude <excluded teams>  comma separated list of teams to exclude
  --include <included teams>  comma separated list of teams to include
  -x, --over_write            over write the output file if it exists
  -C, --count_items           count items instead of summing effort
  -p, --planned <days>        extra days to count from the start of the sprint for planned work (default: 0)
  -l, --late <days>           extra days to count from the end of the sprint for late work (default: 0)
  -h, --help                  output usage information

Invoking

$ tftools velocities -f ~/Desktop/velocities.csv -c 4 -x -p 3 -l 2   --pat iszadpfub08adfsdgf7ybh9adfh9ahf6l3273c2nrxjphlqa --domain https://dev.azure.com/contoso  --project ContosoScrum --exclude "Data Center Engineering,Business Systems"
  • This will get the data for the last 4 sprints for all teams except "Data Center Engineering" and "Business Systems." It will count anything completed 2 days after the sprint end as "late" and will include anything added to the backlod 3 days after the sprint start.

Using as a module

Example for getting the velocities for all teams in a project:

Make a file with this contents in the new directory:

var tfsOpts = {
   ADO_HOST            : “YOUR DOMAIN”, //your domain for ADO, ex: https://fabrikam.visualstudio.com
}

tfsOpts.PAT = “PAT VALUE”; //your ADO PAT

const ADOToolsModule = require(“tftools”)

var velocityOpts = {
   outFile : `~/Desktop/2velocities.csv`,
   projectId:“PROJECT NAME”, //The name of your project, ex: MBScrum
   count : 2
}

void (async()=>{
   let ADOTools = ADOToolsModule(tfsOpts)
   let results = await ADOTools.velocities(velocityOpts)
})();

update the contents of the file, including count and PAT

after that, either debug from your nodejs environment, or run node NAME_OF_YOUR_FILE in the terminal