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

issue

v0.0.6

Published

Command line tool for displaying issues using the issuemd library

Downloads

273

Readme

issue

Command line tool for displaying issues using the issuemd library.

GitHub plugin is included.

issue can be extended with plugins for different issue tracking systems.

Installation

$ npm install -g issue 

Usage (GitHub plugin)

List issues from local GitHub repo

cd into local GitHub repo and run the list command...

$ cd bootstrap
$ issue github list

List issues from online GitHub repo

Specify the target project with the --repo flag

$ issue github list --repo twbs/bootstrap

Show individual issue

To show individual issue, add the issue number as the last argument...

$ issue github show --repo twbs/bootstrap <issue-number>

... or from within github project ...

$ issue github show <issue-number>

Show filtered list of issues

The list command supports standard GitHub filters: 'filter', 'state', 'labels', 'sort', 'direction', 'since'

$ issue github list --state open

Locate repositories

$ issue github locate <search-term>

Locate command can be used to find any repositories on GitHub.

Standard GitHub filters are supported: 'in', 'size', 'forks', 'fork', 'created', 'pushed', 'user', 'repo', 'language', 'stars'

For example, to find all repositories containing bootstrap keyword written in assembly.

$ issue github locate bootstrap --language assembly

Limit check

If you are not logged in, GitHub limits you to 60 core requests per half hour, but if logged in, you get 5000.

$ issue github limit

Output:

core requests: 27/60, resets in: 24 mins
search requests: 10/10, resets in: 2 mins

GitHub login

$ issue github login

To increase the request limit, and get access to your own private repositories you should login with your GitHub credentials.

GitHub login creates a personal access token for issuemd on your GitHub account. Personal access tokens are named:

$ issuemd/issue-<username>@<computer-name>

This enables you to login and use issue from multilple locations at the same time.

GitHub logout command clears out credentials from your .issuerc configuration file.

$ issue github logout

Personal issues

Once you are logged in, you can list all your assigned issues in all projects.

$ issue github list mine

Configuration

Change directory to where you want to store your configuration, and run init command...

$ issue init

This will create .issuerc configuration file in your current directory - typically your home folder, or in a project folder to create overrides.