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

cli-release-note

v0.2.2

Published

Cli to help creating meaningful realese note visually

Downloads

4

Readme

CLI Release Note

CLI tool to help creating release note visually and easily.

[!WARNING] This tool is in Beta release, and main contain issues, feel free to open your own PR to help fix it.

How it works

It uses the outpout of a git log between tags or branches to input data into a static website, and then it opens this website locally in your default browser so you can visually selected the commits and create more readable release notes easily.

Install

Install the package globally, to be able to run it from any repository.

npm install cli-release-note -g

Run

Open the terminal inside a git repository, cli-release-note uses the local git data and commands to generate the commits preview for you.

Now input the release into your terminal:

release -current tag/branch -latest tag/branch

eg:

release -current v1.2.0 -latest v.1.1.0 
release -c v1.2.0 -l v.1.1.0 
release -current feature/Login-page -latest main 

After running the command if everything goes without error, a new tab will open in your default browser, listing all the commits from the tags/branches, and a text editor to easily create your releases note.

Command arguments

Arguments | Alias | Description --- | --- | --- current | c | the current tag or branch to be released latest | l | the latest tag or branch on production to be released

[!WARNING] cli-release-note does a git log [current]..[latest] diff comparison.

In case of no tag or branch match, the terminal you show you the git error, if you are referring to a local tag or branch, make sure you have it locally.

Run project locally

Install all dependencies

npm ci

This project consist in two parts, the CLI that will gather information from git and create a js file with all commits inside an array.

And the web app that presents the commits from the created file and the text editor.

CLI

cli.js contains the logic of the cli, it's a plain js run by node when the user enters "release" in the terminal.

To test changes locally first build the project:

npm run build

Then install the package globally:

npm install -g .

Now you can run the release command in your terminal. When making to change to cli.js build it again with this command:

npm run build:cli

This will make sure to add your changes you mad inside cli.js to the build, without re-building the entire web app

Web App

Assuming you have installed all dependencies, run:

npm run dev

This will start a server on port 9000, with the web app, using a fake content, that comes from ./src/git-log.js, or if you have run the command before, will show the latest commits from that time.