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

simple-release

v1.2.0

Published

An npm module for managing release of nested projects

Downloads

7

Readme

:rocket: simple-release

An npm module for managing release of nested projects

Dependency Status

Why

This was built out of my personal frustration in manually writing changelogs for our project releases. What we have is multiple repositories for different projects and a base repository where all the code is combined before release. Instead of maintaing changelog's for tens of different projects in their own github releases, what this does is combine the latest commits of the base project and all dependent projects and combine them into one changelog, which is used to maintained in the release of the base repository.

Example

Lets say you have a Project Base. There is SubProject 1 and SubProject 2 which are included within Project Base before release. What simple-release aims to do is generate a changelog for each: Project Base, SubProject 1 and SubProject 2. This is then used to create a tagged release in github.

How it works / Setup

Install this module using: npm install -g simple-release

Step 1:

This releases needs access to your github account for creating releases and writing to your project repository. So you will need to create and add your github token to the environment variable GITHUB_TOKEN. For more info, check this article

Step 2:

Go to your base project and type:

$ simple init

This will interactively help you setup your project for use with this module.

Setup screenshot

Thats it. You're all set to start doing hassle free releases!

How to Release

Go to your base project and type:

/* Run for every subsequent releases
 * 'type' is a semver release type
 * Suported values for type: major, premajor, minor, preminor, patch, prepatch, or prerelease
 * Default type is 'patch'
 */
$ simple release <type>

This will:

  1. pick all the latest commits since the last release for your base project and all your sub-projects
  2. create a new semver tag based on the release type
  3. update your package.json with the new tag
  4. create a tagged release with a changelog

Contributions

Suggestions/ideas on how to make it better are most welcome. :)