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

alfred-jira-issue-list

v1.3.2

Published

JIRA

Downloads

12

Readme

Alfred JIRA Issue List

  • 🔎 Quickly look-up tickets from your JIRA board
  • 📋 Copy JIRA ticket numbers
  • 🌍 Instantly open tickets in your browser

Setup

NOTE Ensure you're using Alfred v4 or later and that Alfred has access to a version of Node (>=12)

  1. Install the workflow from npm: npm install --global alfred-jira-issue-list
  2. Configure the workflow variables in 'Workflows' -> 'Workflow Issue List' -> ⒳

Running

  • Within alfred, use the JIRA keyword to bring up results
  • Filter results by key, status or description
  • Cmd-C to copy the highlighted issue key
  • Enter to open the issue in the browser

Troubleshooting

In general you may find it useful to use the Alfred Debugger for most issues.

See: https://www.alfredapp.com/help/workflows/advanced/debugger/

"Library not loaded" error

You may see an error when running the workflow, similar to the following:

Code 134: dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.62.dylib
  Referenced from: /usr/local/bin/node
  Reason: image not found
./node_modules/.bin/run-node: line 49: 69016 Abort trap: 6           ESM_OPTIONS='{"await":true}' node --require esm "$@"

Ensure Alfred has access to a version of NodeJS by installing one through Brew, or upgrading to a compatible version:

brew upgrade nodejs