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-deployer

v0.4.0

Published

Grunt plugin deploying files with versions and specific parameters.

Downloads

2

Readme

grunt-deployer

Grunt plugin deploying files with versions and specific parameters. Can also produce dynamic file names from config.

About

This plugin is used in solid web-base, a grunt boilerplate for solid web applications.

The plugin is a lot about config so we recommand using grunt-minimal-config

Config example

deployer: {
	options: {
		// Files we need to process
		// Keep it simple, no expand
		files: [
			{
				src: '{= path.deploymentFiles }.htaccess',
				dest: '{= path.deploy }.htaccess'
			},
			{
				src: '{= path.deploymentFiles }.spec',

				// Note that templating works in detination files !
				dest: '{= path.deploy }%%specName%%.spec'
			}
		],

		// Auto-incremented version file (this file have to be semver formated, ex : "0.1.0")
		// By default, version is not modified.
		// Pass --patch in your CLI to increment patch number
		// Pass --minor in your CLI to increment minor number
		// Pass --major in your CLI to increment major number
		// Semver format : major.minor.patch
		versionFile: '{= path.deploymentFiles }version',

		// Delimiters (use regex notation)
		// Use only if you really need
		// delimiters: ['\%\%', '\%\%'],

		// Properties common for all targets
		properties: {
			specName : 'specTestName',
			bddLogin: 'root',
			bddPassword: ''
		}
	},

	// This task is only here to bump version but does deploy anything
	// To just increment and deploy nothing :
	// grunt deployer:increment --patch
	increment: { },

	// Different environment examples with different properties :

	// grunt deployer:local
	local: {
		properties: {
			baseURL : '/local/base/path/'
		}
	},

	// grunt deployer:staging
	staging: {
		properties: {
			baseURL : '/staging/base/path/'

			// Override common property
			specName : 'staging-specTestName'
		}
	},

	// grunt deployer:production
	production: {
		properties: {
			baseURL : '/'

			bddLogin: 'production',
			bddLogin: '!p@$$W0rD!'
		}
	}
}

Version

Incremented version file is injected in properties with key "version". Usefull for destination files or to track version in your runtime.

Templating

By default delimiters are %%myVar%%.

Exemple for the .htaccess file :

## Version %%version%%
RewriteBase %%baseURL%%

With the previous config, if you pass grunt deployer:local in your CLI, the output file will be :

## Version 0.1.2
RewriteBase /local/base/path/

Usage

Deploy for local env, no version increment :

grunt deployer:local

Deploy for local env, incrementing patch (0.0.X) :

grunt deployer:local --patch

Deploy for pre-production env, incrementing minor (0.X.0)

grunt deployer:preprod --minor

Deploy for production env, incrementing major (X.0.0)

grunt deployer:prod --major

Deploy for production, without incrementing

grunt deployer:preprod

Deploy nothing but just bump version number

grunt deployer:increment --minor