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

version-manager

v1.7.0

Published

version-manager.

Downloads

16

Readme

version-manager 1.7.0

Updates versions across multiple files.

Install

npm install -g version-manager

Usage

You need a versions.json, or a versions.yml where you can specify for what you're tracking the versions, and what files to be updated using glob patterns:

germanium:
  version: 1.10.3
  files:
    "README.*": "^(germanium )(.*?)$"
    "setup.py": "version='##VERSION##',"
    "doc/usage/index.adoc": "^(= Germanium v)(.*?)$"
    "germanium/version.py": "current = \"##VERSION##\""

Specifying Versions

The version will be expanded using the shell if it contains a '$' or a '`', so you can have a version such as:

"description": {
  "version": "Build at $(date) on $(uname -n)"
}

Versions can also refer to other version files, and extract properties from there, using the parent: notation in the version:

"germaniumdrivers": {
  "version": "parent:../germanium/@germaniumdrivers"
}

The path will point to the versions.json/yml file, or to the folder that contains the versions.json/yml file, and the germaniumdrivers version will be used.

Versions can be also manually overriden from the command line, using the --set or -s flag, for example:

version-manager -s germanium=2.0.8

This will ignore the value specified in the versions.yml file, and use the specified one.

File Matchers

There are currently only four file matchers:

RegExp File Matcher

It is a RegExp that has two or three groups, and it will have the second group replaced to the matched version.

VERSION File Matcher

This will construct a RegExp that will match exactly the given text, with the **VERSION** being the second group.

So having a matcher such as:

"files": {
    "README": "This installs version **VERSION** of the product."
}

is equivalent with:

"files": {
    "README": "(This installs version )(.+?)( of the product\\.)"
}

If the **s are replaced with ^^ at the beginning, or $$ at the end, they will act as RegExp anchors, equivalent to ^ and $. In case in the expression there is content before the ^^, or after the $$, the content is ignored.

maven: File Matcher

This will construct a RegExp that will match:

`(<groupId>${m[1]}</groupId>\\s*` +
`<artifactId>${m[2]}</artifactId>\\s*` +
`<version>)(.*?)(</version>)`;

In order to specify the matcher, just use:

germaniumY
  version: 2.0.0
  files:
    pom.xml: maven:com.germaniumhq:germanium

Matcher Constraints

In order to make sure that the expressions are not replacing in too many places, constraints can be added to limit, or extend the matches.

Matcher constraints are always active, and in case no constraint is specified then the maximum replacement count is set to 1.

Match Count

"product" : {
  "version": "1.0",
  "files": {
    "README.md": {
      "match": "^(= Germanium v)(.*?)$",
      "count": 1
    }
  }
}

The count can be also 0 for no matches, or negative to indicate any number of matches is allowed.

Multiple Matchers

In a single file, we can have multiple matchers as well, for example:

"product" : {
  "version": "1.0",
  "files": {
    "README.md": [
      "^(= Germanium v)(.*?)$",
      "(Germanium )(\\d+\\.\\d+)()"
    ]
  }
}

For each matcher that is added, if there is no match count specified, it's assumed that it will only match once in the file.

Of course, constraints can be applied for both the full set of matchers:

"product" : {
  "version": "1.0",
  "files": {
    "README.md": {
      "match": [
        "^(= Germanium v)(.*?)$",
        "(Germanium )(\\d+\\.\\d+)()"
      ],
      "count": 3
    }
  }
}

or even individual expressions:

"product" : {
  "version": "1.0",
  "files": {
    "README.md": {
      "match": [
        "^(= Germanium v)(.*?)$",
        {
          "match": "(Germanium )(\\d+\\.\\d+)()",
          "count": 2
        }
      ],
      "count": 3
    }
  }
}

Notes

  1. Files are actually glob patterns, so you can match **/*.js for example.
  2. The configuration files can be yml.
  3. version-manager will output the following error codes: 0 when no files are changed, 200 when files are changed successfuly, or a non zero error code in case of error.