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

changelog_output

v1.4.0

Published

A module created to convert a standard version changelog to a more readable ouput for a more product focused view.

Downloads

3

Readme

Changelog Output

A module created to convert a standard version changelog to a more readable ouput for a more product focused view.

This checks for changes between the new version and last version.

Usage

./node_modules/.bin/cogenerate

or add as a script to run inside of npm package.json

"script": {
	...,
	"generate": "./node_modules/.bin/cogenerate"
}

Options

There are 4 options you can provide to the generate either as command line args or as a co-config.json file.

NOTE: Slack webhooks are secret URLS and should not be allowed in the config file. Pass as an arg for safety.

Link is built off the assumption that you are using jira. How this works is it looks for the ticket number inside of description of your commit and if it exists it will append that value to the end of the link property.

Config

In the root directory where you run this command add a co-config.json file.

{
	"writeOutput": false,
	"fileName": "CHANGELOG.md",
	"link": "https://some/path/to/"
}

Command line args

Command line args are the same values as the config but allows one more option for slack webhook integration.

Slack integration already uses the following value as a base so you just need to provide the secrets portion. https://hooks.slack.com/services/

npm run generate -- --writeOutput false --fileName CHANGELOG.md --link https://some/path/to/ --slack my/secret/ending/url

Link

As stated above the link is under the assumption you are using Jira.

The regex pattern inside of commit descriptions is

/([a-zA-Z]+(-[0-9]+)+)/g

This is appended to the end of the link value you provide.

Example

{
	"link": "https://something.atlassian.net/browse/"
}

commit message
feat(thing): POS-43 The coolest feature ever

Output link value will be
https://something.atlassian.net/browse/POS-43

NOTES

If this is the first time you are running and just ran the first release command for standard version you will need to add one small change due to the regex pattern.

This is because the first release does not have anything to compare against and breaks the simple regex being used.

So a simple update is the following:

  • Run the first release command for standard version.
  • Bottom of the file will output just the starting version "## 0.0.0"
  • Update to be something like "## 0.0.0 [0.0.0](some_link) (2022-05-16)"