node package manager


Shared configuration to help deploy Glazier Cards


Shared grunt configuration for glazier cards.


You will need your package.json to add dependencies for the grunt task libraries being used:

npm install --save-dev grunt-contrib-jshint grunt-es6-module-transpiler grunt-contrib-concat grunt-contrib-clean grunt-contrib-copy
npm install --save-dev grunt-ember-templates grunt-contrib-handlebars grunt-md5 grunt-s3

Add this to your package.json to include this module:

npm install --save-dev glazier-card-grunt-config

Your card's package.json should contain a glazierConfig options object. The consumes, assetHost, shortName and repositoryName keys are required. An example looks like:

"glazierConfig": {
  "consumes": [
  "assetHost": "",
  "shortName": "github-issues",
  "repositoryName": "yapplabs/github-issues"

In order to use the deploy task, you need to set environment variables with details for your bucket:


Placing the following in your Gruntfile.js will give you the standard set of card grunt tasks:

var glazierCardGruntConfig = require('glazier-card-grunt-config'),
  sharedConfig = glazierCardGruntConfig.createSharedConfig(grunt);


Developing Outside of Glazier

Run grunt autotest in your card's repository to start a server hosting only your card's tests at http://localhost:8000.

Tests that allow themselves to be run in phantom will also automatically run on the command line.


  • build - copies concatenated assets into dist folder for use in dev
  • manifest - fingerprints assets and creates a manifest describing them
  • deploy - creates the manifest and fingerprinted assets and uploads them to S3