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

status-update

v1.0.3

Published

Turns issues into links in did output. Will be obsolete if [psss/did#164](https://github.com/psss/did/issues/164) is ever resolved.

Downloads

6

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

achingbrainachingbrain

Keywords

Readme

status-update

Turns issues into links in did output. Will be obsolete if psss/did#164 is ever resolved.

Pre-requisites

  1. A working did install
  2. Slack set to parse mark~~down~~up by default

Usage

By default it will format the output of did today:

$ status-update
Status Update:

* Pull requests created on github: 46
...

Any forward args will be passed to did:

$ status-update year
Status Update:

* Pull requests created on github: loads
...

Copy/paste the output into your update channel and you are done!

Showing full PR/Issue titles

If no --width argument is passed, --width 5000 is used to show the whole title of issues and PRs

But it uses issues for all the links

No worries - GitHub is kind enough to not use the same number ranges for issues and PRs so it will forward you to the right page.