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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@jvmn/groundzero-changelog

v2.1.0

Published

Changelog generator for JvM/Neckar Groundzero projects

Readme

Jung von Matt/Neckar - GroundZero Changelog

What is this script doing?

Bumps the release version depending on the type of commits found and writes all the commits to a changelog file in Markdown format.

How is it doing it?

  1. Gets the last release tag from the package.json and scans all commits from the git HEAD to that point.
  2. From the commits determines what type of release it should be and bumps the package.
  3. Formats the commits to markdown and writes to CHANGELOG.md

Installation

  1. npm install:

    npm install @jvmn/groundzero-changelog --save-dev
  2. add a script to the scripts section in your package.json

    "postrelease": "groundzero-changelog",

    or any other hook you want to run it from.

  3. *optionally run standalone nextSteps log via:

    "groundzero-changelog-next"
  4. *optionally overwrite default options in package.json

Options

In your main project package.json you can overwrite some defaults by adding the jvmChangelog object. Defaults to:

"jvmChangelog": {
    "logNextSteps": "true",
    "pathChangelog": "./docs/CHANGELOG.md",
    "pathRepo": "./.git",
    "gitRepo": "false",
    "gitPlatform": "bitbucket",
    "ignores": ["build", "chore", "revert", "test"],
    "extraComments": []
},

The gitRepo url used to generate Bitbucket/ Github links. Fractal config is not used anymore.

gitPlatform responsible for the url format outputed on commits and version compare, by default uses "bitbucket" but now supports also "github".

extraComments accepts an array with strings and generates extra comment lists automaticly (which you would fill manually) and prints them before the commit groups in each relase.

logNextSteps if set to false will not print the next steps log at the end of the task. Instead one can run it at a later date via the node command "groundzero-changelog-next"

Script assumptions

  • Your commits follow the Angular Commit Message Conventions (https://gist.github.com/stephenparish/9941e89d80e2bc58a153)

  • A Jira ticket is written inside brackets [TICKET-123] and can be located anywhere in the commit.