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

@falcucci/changelog-it

v1.8.4

Published

Generates a changelog by matching git commits to Jira tickets.

Downloads

25

Readme

Changelog-it

Generates a changelog of Jira issues from your git history and, optionally, attach all issues to a release.

For example:

$ changelog-it --range origin/prod...origin/master --release --gmudd --summary "some summary..."

take a look on this file to check how it will looks like

You can also have it automatically post to slack!

How it works

The script looks for Jira issue keys, surrounded by square brackets (i.e. [DEV-123]), in the git commit logs. When it finds one, it associates that Jira issue ticket with that commit and adds it to the changelog.

Installation

npm install -g -S @falcucci/changelog-it

Configuration

You'll need to configure Jira before you can use this effectively. Create a file called changelog.config.js and put it at the root of your workspace directory; where you'll call the jira-changelog command from.

Here's a simple example with sample Jira API values:

module.exports = {
  jira: {
    api: {
      host: "yoursite.atlassian.net",
      username: "jirauser",
      password: "s00persecurePa55w0rdBr0"
    },
  }
}

To see all values suported, look at the changelog.config.js file at the root of this repo.

Usage

changelog-it --range origin/prod...origin/master --slack --release

Assuming you deploy from the prod branch, this will generate a changelog with all commits after the last production deploy to the current master version.

If you define sourceControl.defaultRange in your config, you can run the command with the --range flag:

changelog-it

Releases

You can automatically attach Jira issues to a release with the --release flag. For example, let's say we want to add all issues in the changelog to the "sprint-12" release:

changelog-it --range origin/prod...origin/master --release sprint-12

This will set the fixVersions of all issues to "sprint-12" in Jira.

Slack

You can also have the script automatically post to slack.

First, get an API token from Slack for your workspace: https://api.slack.com/tokens

Then add slack to your configuration file:

module.exports = {
  slack: {
    apiKey: 'asdlfkjasdoifuoiucvlkxjcvoixucvi',
    channel: '#changelogs'
  },
  jira: {
    api: {
      host: "myapp.atlassian.net",
      username: "jirauser",
      password: "s00persecurePa55w0rdBr0"
    },
  }
}
  • Add your API token to slack.apiKey.
  • slack.channel is the channel you want the script to send the changelog to.

Then simply add the --slack flag to the command:

changelog-it --range origin/prod...origin/master --slack

You can automate it generating semantic version tags using the following command:

curl -LsS https://raw.githubusercontent.com/falcucci/release-me/master/changelog-it.sh | bash -s <semantic-version> <summary>

or creating an alias in your .aliases file:

alias release-me='curl -LsS https://raw.githubusercontent.com/falcucci/release-me/master/changelog-it.sh | bash -s $1 $2'

and run:

release-me <semantic-version> <summary>

GitLab CI

note: this requires npm to run+

Store the following envs in GitLab CI variable.

| name | description | | ---- | ----------- | | GITLAB_API_KEY | Gitlab api key | | SLACK_API_KEY | Slack api key | | SLACK_CHANNELS | Slack channels ids separeted by comma | | GMUD_CHANNEL | Slack gmud channels ids separeted by comma |

.gitlab-ci.yml sample

changelog:
  script:
    - changelog-it v1.0.0...v2.0.0 --release --gmud
    # Or using aliases above if you have it in a package.json
    - npm run changelog
    # Or using some script
    - curl -LsS https://raw.githubusercontent.com/falcucci/release-me/master/ci-changelog-it.sh | bash -s

You can use changelog-it to generate changelogs and gmuds from anywhere with following environment variables.

$ export GITLAB_API_KEY=haya14busa
$ export SLACK_API_KEY=haya14busa
$ export SLACK_CHANNELS=APOISFDUP
$ export GMUD_CHANNEL=PAOISUFOPUAS

API

The code used to generate the changelogs can also be used as modules in your JavaScript. See the module source for documentation.

For example:

npm install -S @falcucci/changelog-it
const Config = require('@falcucci/changelog-it').Config;
const SourceControl = require('jira-changelog').SourceControl;
const Jira = require('jira-changelog').Jira;

const gitRepoPath = '/home/user/source/'

// Get configuration
const config = Config.getConfigForPath(gitRepoPath);

// Get commits for a range
const source = new SourceControl(config);
const range = {
  from: "origin/prod",
  to: "origin/master"
};
source.getCommitLogs(gitRepoPath, range).then((commitLogs) => {

  // Associate git commits with jira tickets and output changelog object
  const jira = new Jira(config);
  jira.generate(commitLogs).then((changelog) => {
    console.log(changelog);
  });

});