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

offline-issues

v1.0.0

Published

Clone GitHub Issues locally for offline perusal

Downloads

13

Readme

offline-issues

js-standard-style

Get your GitHub Issues offline! In Markdown and HTML.

This is a command line application, using Node.js, that fetches the GitHub Issue/s you specify and writes them to files on your computer in both HTML and markdown formats. This way you can view them without an internet connection.

This will cap issues at the first 250.

screenshot

To Use

  • Have Node.js installed on computer.
  • From your command line, install this module npm install -g offline-issues
  • Authorize it by running offline-issues and following the commands.
  • Use it to save Issues as .md and .html. Options in next section.

Command Line Interface (CLI)

For one issue:

$ offline-issues USER/REPO#0

For all issues:

$ offline-issues USER/REPO

For multiple repositories or issues:

$ offline-issues USER/REPO USER/REPO#0

Example:

$ offline-issues jlord/offline-issues muan/github-gmail#4

The files are written to whichever directory you are currently in. You will see a md and html folder added, each of with contains the issues you requested.

Options

To just generate HTML files from existing offline cache:

$ offline-issues -h
$ offline-issues --html

To skip generating static files for HTML:

$ offline-issues -S USER/REPO
$ offline-issues --no-static USER/REPO

To filter by issue state:

$ offline-issues -s all USER/REPO
$ offline-issues --state all USER/REPO

This option accepts either open, closed or all. (Default: open) Note that the filter won't be applied when issue number is specified, like muan/github-gmail#4.

Build / Develop Locally

  • Clone this repository: git clone https://github.com/jlord/offline-issues.git
  • Go inside this project: cd offline-issues
  • Install dependencies: npm install
  • Link this local version to your global npm link (or sudo npm link)
  • If you have trouble with this or don't want to override the published version (this one) you can run it through the path to the main file: <path-to-clone>/src/cli.js OPTIONS
  • On Ubuntu, use nodejs <path-to-clone>/src/cli.js (or nodejs $(which offline-issues)) to start the CLI

Future times

Currently working at MVP level -- it gives you the issues you specify. But I want to add (or recieve Pull Requests!) to it:

  • More command line options like getting 'all' or 'closed' or 'open' or by 'author' or 'mention'.
  • Directory/Index of files you have.
  • Tests.
  • Spin up sever.
  • Sync up the issues you currently have at a later date.