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

date-based-version

v2.5.0

Published

Tool to generate date-based versions

Downloads

21

Readme

date-based-version

This library is a tool to help you maintain date-based versions in your git repository.

Date based versioning

Here is how the date-based versioning works:

  • Every commit to master is released.

  • The release version of each commit is stored as a tag.

  • Every commit to master become the source of its own release branch, this allows patching.

  • The version is composed of 4 parts:

    1. always 1
    2. date of the release
    3. release number for this release date
    4. patch number

A git log command show such versioning strategy.


~/demo $ git log --oneline --decorate --graph --all

* 0dd0a2a (tag: v1.20200512.2.0, release/v1.20200512.2, master) fourth commit
* 39ccfc3 (tag: v1.20200512.1.0, release/v1.20200512.1) third commit
* 8d634ca (tag: v1.20200510.2.0, release/v1.20200510.2) second commit
| * 8b5c451 (tag: v1.20200510.1.1, release/v1.20200510.1) patch for first commit
|/
* 96fedff (tag: v1.20200510.1.0) first commit

This tool

Usage:

Call this function from the release pipeline.

  • The new version will be calculated based on the previous version, the date and the patch flag.
  • The commit will be tagged with the version.
  • If the --patch flag is not provided, a release branch will be created.
  • When you provide a scope through the --scopeTag argument. It will iterate through all the sub scope until it finds a matching tag. This is particularly useful in a monorepo where you would wand to maintain multiple scope. Example your release pipeline produces the following tag: release/v1.YearMonthDay.version and you wish to patch a package using a different tag pattern. You can achieve this by calling npx date-based-version --patch --scopedBranch=release/<team> --iterateOnScope and you will get the following tag: release/<team>/v1.YearMonthDay.version.patch.
# on master
npx date-based-version

# on a release branch
npx date-based-version --patch

# dry run (won't create branch or tag)
npx date-based-version --dry-run

# scope tag by prefix (i.e. scope/v1.20200510.1.0)
npx date-based-version --scopeTag=scope

# scope branch by prefix (i.e. scope/release/v1.20200510.1)
npx date-based-version --scopeBranch=scope