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

origami-logs

v2.2.4

Published

<p align=center><img src="https://s15.postimg.cc/dk2ezad5n/logo.png" width="400"></p>

Downloads

26

Readme

Origami Logs

A github changelog generator for your release notes.

Build Status

Installation

npm i -g origami-logs

First Step

Create a file named .origami-logs-config.json in the root of your project.

The file should look something like this:

{
  "github":{
    "apiUrl": "https://git.somedomain.com/api/v3",
    "token": "123456",
    "repository": "Organization/repo-name"
  }
}

How to use

TO RUN:

changelog generate --tags "startingTag,endingTag"

To see all other options:

changelog generate --help

Config Options Explained

If you wish to add other config options it might look like this:

{
  "github":{
    "apiUrl": "https://git.somedomain.com/api/v3",
    "token": "123456",
    "repository": "Organization/repo-name"
  },
  "aliases": {
    "enhancement": [
      "feature"
    ]
  },
  "extraLabels": {
    "chore": "Chores Completed:"
  },
  "extras": {
    "pivotal":{
      "boardID": "1234567"
    }
  }
}
  • github: REQUIRED The info about the given repository you wish to get the changelog format for markdown
  • aliases: This is to be used if you want to use your own custom labels but still conform to the enhance/bug format.
    • IE: You might have a feature label but still want it to show Features Implemented on the changelog.
  • extraLabels: Define your own custom labels and changelog headings
  • extras: Where additional connections live
    • pivotal: Supports linking pivotal stories in your change log assuming commits conform to the format: [#STORY_ID_HERE] Commit Message here
      • boardID: Pivotal Board ID (Found at the end of the url such as https://www.pivotaltracker.com/n/projects/ID-HERE)

Development

To test locally run

node cli.js generate --tags "TAG1,TAG2"