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

commentary-cli

v0.6.0

Published

This is a small demo that will either create a new comment or update an existing comment on a pull request in GitHub.

Downloads

3

Readme

Commentary - Update a github comment

This is a small demo that will either create a new or update an existing comment on a pull request in GitHub.

I got the idea from Ben Limmer, but I did it in Go.

This seemed like a good way to test how fast the various methods of running github actions would be.

So writing GitHub actions in Go, I'm aware of 4 possibilities:

  1. just shell out and go run main.go
  2. package the Go using npm or like this (private or public npm registry as you please)
  3. package your Go as a docker container (private or public registry)
  4. attach pre-built Go artifacts to a github release and run those using js wrappers

I have started to add all these to this repository to see how they perform.

Running as a GitHub Action

There are several environment variables that this needs.

  • COMMENTARY_ACTION_TYPE - you can have multiple actions all racing without stepping on each other
  • GITHUB_TOKEN - This should be a secret, but is the personal access token of the service account (or your real github account)
  • GITHUB_REPOSITORY - Set by GitHub as an owner/repo
  • GITHUB_REPOSITORY_OWNER - Set by GitHub as owner
  • GITHUB_BASE_REF - Set by GitHub as main
  • GITHUB_HEAD_REF - Set by Github to be the branch name, e.g. mybranch
  • GITHUB_REF_NAME - Set by Github, for example, 1/merge
  • GITHUB_SHA - Set by GitHub as the commit sha1, and used to look up the PR.

Mage

Instead of make and Makefile, I used mage and made a magefile.

If you do brew install mage then you can run here:

  • mage -v run - will run the webserver by doing go run main.go
  • mage generate - will re-generate the genqlient code by doing go generate ./...
  • mage install - will build and install the commentary application binary
  • mage release - will generate a new release

Or just run the go commands by hand.