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

@nhi/todo-to-azure

v0.0.13

Published

Parses code for TODO (and other) annotations, and creates tasks/backlog items on Azure DevOps Boards

Downloads

21

Readme

@nhi/todo-to-azure

THIS IS EXPERIMENTAL ⚠

Parses your code for TODO (and other) annotations, and creates tasks/backlog items on Azure DevOps Boards, under the Current Iteration.

It will write back a URL for the created item into the comment.

Example:

Before:

/**
 * TODO:
 * This must be done!
 */ 

After:

/**
 * TODO: https://dev.azure.com/{organization}/{project}/_workitems/edit/{id}
 * This must be done!
 */ 

And this will be added as a Work Item to organization in project, with id.

Installation

yarn add -D @nhi/todo-to-azure

or

npm i -D @nhi/todo-to-azure

Usage

Usage: todoo [options]

Options:
  -v, --verbose         Verbose logging (default: false)
  -d, --dry             Only show parsed Work Items (default: false)
  -P, --show-processed  Show a list of already processed Work Items (default: false)
  -c, --config          Specify location of config file (default: .todo-to-azure.js)
  -i  --include         Glob pattern for files to parse (default: src/**/*.js)
  -t, --token           Personal Access Token for Azure Devops
                        Required scopes:
                        • Project and Team - Read & Write
                        • Work Items - Read & Write
                        Can be also defined in the config file
  -V, --version         output the version number
  -h, --help            display help for command

If you specify the Personal Access Token token in your config file, be sure the file is gitignored, if your repository is public!

Configuration

You can either use the flags shown in Usage, or use an external file. This is .todo-to-azure.js by default.

It looks like this:

module.exports = {
  include: "path/to/src/**/*.js",
  organization: "ORG",
  teamContext: {
    team: "Team name",
    project: "Project name"
  },
  token: "PERSONAL_ACCESS_TOKEN",
  annotations: ["TODO", "HACK", "BUG", "FIX"]
}

Created by