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

@semantic-release-extras/github-comment-specific

v2.0.4

Published

[![Build Status]](https://github.com/semantic-release-extras/github-comment-specific/actions/workflows/release.yml)

Downloads

2,513

Readme

@semantic-release-extras/github-comment-specific

Build Status

This is a drop-in replacement for the standard @semantic-release/github plugin. It exists to add specificity to the GitHub issue and PR comments, so instead of commenting that

This PR is included in version {version}

it comments

This PR is included in version {package}@{version}

Why?

I agree, this seems like a small improvement. However, when using semantic-release with a multirepo^1 the default behavior adds several comments like this to a PR:

which is downright confusing.

With @semantic-release-extras/github-comment-specific, the comments look like:

Much better!

Install

npm install --save-dev --save-exact @semantic-release-extras/github-comment-specific

Use

@semantic-release-extras/github-comment-specific is just a wrapper, so it inherits the API contract of @semantic-release/github.

For example:

{
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    "@semantic-release/npm",
    "@semantic-release/git",
    "@semantic-release-extras/github-comment-specific"
  ]
}

Alternatives

Template string

It may be possible to use the stock @semantic-release/github plugin with configuration like:

[
  "@semantic-release/github",
  {
    "successComment": ":tada: This ${issue.pull_request ? 'PR is included' : 'issue has been resolved'} in version ${nextRelease.gitTag}</br></br>The release is available on [${releases[0].name}](${releases[0].url}) :tada:</br></br>Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:"
  }
]

Note: This configuration is untested.

However, the templating options offered by the stock plugin leave something to be desired. This template is not one-to-one with @semantic-release-extras/github-comment-specific in terms of features or flexibility.

Upstream the changes

Wouldn't it be better to upstream these changes?

Yep, definitely. The upstream repository has a high load:maintainers ratio at the moment, and this plugin exists here and now.