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 🙏

© 2025 – Pkg Stats / Ryan Hefner

ticket-notes

v1.0.1

Published

Easily ticket notes

Readme

ticket-notes

A simple NPM package to template your notes

How to use

Just use the command "entry" with the GitHub pull request title, followed by any files you used in the ticket.

which will output the following for you to copy into whatever document you like:

ticket-1234 https://ticketing-site.com/ticket-1234
Name: Do some stuff to the things
Date: 10/20/18
Description:
Fix:
Files:
MY-REPO
/file1
/file2
Commits: https://github.com/mostlyfocusedmike/my-repo/pull/102/commits

Install

You have to globally install using npm install -g ticket-notes

Environment Variables

ticket-notes expects several environment variables to be set, and will throw an error if any are missing:

  • PARENT_DIR

In order to grab your repo names, ticket-notes assumes there's a parent project folder. If your repo is in ~/Desktop/my-projects/my-repo, then PARENT_DIR=my-project (no leading/trailing slashes)

  • BOARD

This is the kanban board site that is used to manage your tickets. If your url is https://coolkanban.company-name.com/tickets/ticket-123, then BOARD=coolkanban.company-name.com/tickets (no leading/trailing slashes)

  • GITHUB_PROFILE

This is just whatever your GitHub profile name is, so mine is GITHUB_PROFILE=mostlyfocusedmike

PR Title format

The string must follow this format:
"[ticket-number] ticket name #pull-request-number"
Luckily, the PR number is automatically included by github, so if you name your PR after your ticket, this is just a simple cut and copy.

Files

As long as your file path contains your PARENT_DIR, it'll work fine:
good: ~/Desktop/parent-dir/repo-name/file
good: /parent-dir/repo-name/file
good: parent-dir/repo-name/file
bad: repo-name/file

The reason for this is that it's optimized for the VS Code's "copy path" option, so it's expecting a full file path. For ticket-notes to work, you must include a properly formatted PR string, as well as at least ONE file.