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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@changesets/changelog-github

v1.0.0

Published

A changelog entry generator for GitHub that links to commits, PRs and users

Readme

@changesets/changelog-github

Open on npmx.dev View changelog

A changelog generator for Changesets that links to GitHub commits, PRs, and authors.

Usage

The @changesets/changelog-github package requires a GITHUB_TOKEN with read:user and repo:status permissions. Add it to your repository's GitHub Action secrets and your .env file:

GITHUB_TOKEN=token_here

Then you can use it in the changelog option:

{
  "changelog": ["@changesets/changelog-github", { "repo": "owner/repo" }]
}

Options

repo

  • Type: string
  • Default: process.env.GITHUB_REPOSITORY

Specify the <org>/<repo> slug of your GitHub repository. If you intend to run this locally, specify the option explicitly or set the GITHUB_REPOSITORY environment variable.

When running in GitHub Actions, GITHUB_REPOSITORY is automatically set, so you can omit this option if you are only running in GitHub Actions.

disableThanks

  • Type: boolean
  • Default: false

Set true to drop the "Thanks [@user]!" attribution from each line.

[!NOTE] It is recommended to not set "disableThanks": true when using the template option as the {authors} token would return an empty string, which could lead to unexpected results.

template

  • Type: string
  • Experimental

[!WARNING] Experimental. The template option and its token syntax may change in any release, including a patch. If you rely on it, pin the exact @changesets/changelog-github version.

This option allows you to customize the format that should be used for the generation of a single changelog line. For example, the default template generates this Markdown:

- [#123](https://github.com/<org>/<repo>/pull/123) [`a1b2c3d`](https://github.com/<org>/<repo>/commit/a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0) Thanks [@ghost](https://github.com/ghost)! - fix the thing

Each piece of information can be dynamically represented with tokens. The above example can be represented as:

\n\n- {pull} {commit} Thanks {authors}! - {summary}

Tokens

The template option supports these tokens.

| Token | Description | Example | | ----------- | ---------------------------------------------------------------------------------------------- | -------------------- | | {summary} | The first line of the changeset Markdown content. | fix the thing | | {ref} | Link to either the PR or commit (if the changes were pushed directly). Wrapped in parenthesis. | ([#123](url)) | | {pull} | Link to the PR if available. | [#123](url) | | {commit} | Link to the commit. | [`abc1234`](url) | | {authors} | Link to the GitHub user profile of the main author of the commit (and PR). | [@ghost](url) |

[!NOTE] If a token is used and its data is absent, the token will generate an empty string. The continuation lines of a multi-line summary are also always appended below the template, indented by two spaces.

Examples:

| template | Generated Markdown | | ------------------------------------------------------- | ----------------------------------------------------------------------------- | | "\n\n- {pull} {commit} Thanks {authors}! - {summary}" | \n\n- [#123](url) [`abc1234`](url) Thanks [@ghost](url)! - fix the thing | | "\n\n- {summary} {ref}" | \n\n- fix the thing ([#123](url)) or - fix the thing ([`abc1234`](url)) | | "\n\n- {summary} (thanks {authors}!)" | \n\n- fix the thing (thanks [@ghost](url)!) | | "\n\n- {summary} {pull}" | \n\n- fix the thing [#123](url) |