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

chalogen

v0.2.2

Published

CHANGELOG.md generator CLI and Github Action

Downloads

25

Readme

chalogen

CHANGELOG.md generator CLI and Github Action

Keeping CAHNGELOG.md file in your repository is very important to inform users what happened in your code from version to version. Doing it manually is hard work, but using Chalogen you will get pretty changelog based on your commits.

  • Parse conventional commits
  • Supports version commits like from npm version command.
  • Available as CLI tool or GitHub Action
  • Supports tags named in semver format
  • Supports Git emojis

Conventional commits

Chalogen will parse all your commits, but better result will be with conventional commits. If work with VSCode, there is nice extension to help you making such commits. If commits doesn't matched as conventional, it is just goes to other type group.

CLI

Install globaly with:

npm i -g chalogen

Then run in your local repositroy folder:

chalogen

And you will see new CHANGELOG.md file with versions history.

It is important to have full commits history in your local repository.

Look for additional parameters with chalogen --help command.

GitHub Action

It is good idea to run Chalogen in GitHub Action to have always actual changelog file in your repository. Just add and commit file .github/workflows/generate_changelog.yml in your GitHub repository:

If you installed CLI you can just run chalogen action to put exactly same file in your current repo.

name: Generate Changelog

on:
  push:
    branches: [ main, master]

jobs:
  changelog:
    name: Update Changelog
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2
        with:
          fetch-depth: 0
      - name: Update Changelog
        uses: AlexxNB/chalogen@master
        with:
          title: My project changelog 
      - name: Commit Changelog to repository
        uses: stefanzweifel/[email protected]
        with:
          commit_message: 'docs(Changelog): Update Changelog'
          file_pattern: CHANGELOG.md

Input parameters

  • title – Title of changelog. Default: Changelog
  • list – Conventional types list to include in changelog. Default: feat,fix,perf,docs,other
  • date – Date format; use only %Y,%M and %D placeholders. Default: %Y-%M-%D
  • file – Filename of the changelog file. Default: CHANGELOG.md
  • version – Show only specified version. Default: false
  • unreleased – Show only unreleased commits. Default: false
  • hide-unreleased – Hide unreleased section. Default: false
  • hide-title – Hide title of changelog. Default: false
  • hide-body – Hide body of commit's messages. Default: false

Output parameters

  • changelog – changelog history in markdown format, which may be used in next workflow steps(ex. as release body).