Go to file
Tyler Kellen 6b5f9b1944 Merge pull request #3 from lazd/nstmpl
Flexible namespaces for templates
2012-09-15 13:06:47 -07:00
tasks Use getNamespaceDeclaration to declare namespace and JSON.stringify to escape template names 2012-09-14 16:31:54 -07:00
test Tests for getNamespaceDeclaration, moved expected test results into test/expected 2012-09-14 16:32:44 -07:00
.gitignore first commit 2012-09-10 13:12:23 -05:00
AUTHORS first commit 2012-09-10 13:12:23 -05:00
grunt.js Tests for getNamespaceDeclaration, moved expected test results into test/expected 2012-09-14 16:32:44 -07:00
LICENSE-MIT first commit 2012-09-10 13:12:23 -05:00
package.json version bump and release history 2012-09-12 11:06:25 -05:00
README.md Added detailed information and example for namespace option 2012-09-14 16:36:52 -07:00

grunt-contrib-jst

Compile underscore templates to JST file (part of the grunt-contrib collection). Submitted by Tim Branyen.

Getting Started

Install this grunt plugin next to your project's grunt.js gruntfile with: npm install grunt-contrib-jst

Then add this line to your project's grunt.js gruntfile:

grunt.loadNpmTasks('grunt-contrib-jst');

Overview

This task compiles Underscore compatible templates into functions that can be concatenated and minified with existing source files.

Inside your grunt.js file, add a section named jst. This section specifies the files to compile and the options passed to underscore.template.

Parameters

files object

This defines what files this task will process and should contain key:value pairs.

The key (destination) should be an unique filepath (supports grunt.template) and the value (source) should be a filepath or an array of filepaths (supports minimatch).

Note: Values are precompiled to the namespaced JST array in the order passed.

options object

This controls how this task (and its helpers) operate and should contain key:value pairs, see options below.

Options

namespace string

The namespace, in dot notation, in which the resulting JST templates are assigned to. The example below assigns templates to the MyApp.Templates namespace:

Example:

options: {
  namespace: 'MyApp.Templates'
}
processName function

This option accepts a function which takes one argument (the template filepath) and returns a string which will be used as the key for the precompiled template object. The example below stores all templates on the default JST namespace in capital letters.

options: {
  processName: function(filename) {
    return filename.toUpperCase();
  }
}
templateSettings object

The settings passed to underscore when compiling templates.

Config Examples

jst: {
  compile: {
    options: {
      templateSettings: {
        interpolate : /\{\{(.+?)\}\}/g
      }
    },
    files: {
      "path/to/compiled/templates.js": ["path/to/source/**/*.html"]
    }
  }
}

Release History

  • 2012/08/12 - v0.2.2 - Added processName functionality & escaping single quotes in filenames.
  • 2012/08/10 - v0.2.0 - Refactored from grunt-contrib into individual repo.