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

grunt-simple-version

v0.2.4

Published

Update the project version across multiple files

Downloads

105

Readme

Grunt Simple Version

Dependency Status Build Status npm version

Easily update the version across your project. By default this updates the version field in package.json. Uses Semantic Versioning format.

Requirements

Tasks Setup

Sample Gruntfile.js below. The version can take an optional map of file names as the options for files to update (other than package.json). For updating JSON files, the value is the name of the field to change. For instance, in this example bower.json has a field called version.

module.exports = function(grunt)
{
	grunt.loadNpmTasks('grunt-simple-version');

	grunt.initConfig({
		version: {
			options : {
				'bower.json' : 'version'
			}
		}
	});
};

Tasks Setup Examples

Nested-Field Update (JSON-only)

The target field property on a JSON file can also be nested using a dot-syntax style address. The example below would update a version field on a meta object.

grunt.initConfig({
	version : {
		options : {
			'info.json' : 'meta.version'
		}
	}
});

Cache-Busting Update (HTML-only)

Providing a value of cache-bust to an HTML file will append any src or CSS href properties with the version number. For instance, <script src="main.js"></script> would become <script src="main.js?v=1.0.0"></script>. This will help invalid the browser cache for linked assets.

grunt.initConfig({
	version : {
		options : {
			'deploy/index.html' : 'cache-bust'
		}
	}
});

Replacement Update

A replacement function can be used to replace the version in the contents of a file. The function takes two arguments, the contents of the file and the version number to update to. The function must return an update string with the contents of the file.

grunt.initConfig({
	version : {
		options : {
			'deploy/index.html' : function(content, version) {
				return content.replace(
					/\<\!\-\- Version .* \-\-\>/,
					'<!-- Version ' + version + ' -->'
				);
			}
		}
	}
});

Multiple Updates

The target field also supports multiple options (fields, nested-fields, functions, cache-bust) for a single file. The example below would update two fields in the JSON file with the version and do a dynamic function replacement.

grunt.initConfig({
	version : {
		options : {
			'project.json' : [
				'version', 
				'meta.version', 
				function(content, version){
					content.description = "Current build version " + version;			
				}
			]
		}
	}
});

Usage

Ways to set the version across the project:

# Return the current version
grunt version:current

# Set a specific version
grunt version:1.0.0-rc

# Bump the patch version e.g., 1.0.1 => 1.0.2
grunt version:patch

# Bump the patch version e.g., 1.2.1 => 1.3.0
grunt version:minor

# Bump the patch version e.g., 1.3.0 => 2.0.0
grunt version:major