grunt-yate

grunt-yate

Yate compiler plugin

Getting Started

This plugin requires Grunt ~0.4.1

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-yate --save-dev

One the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-yate');

The "yate" task

Overview

In your project's Gruntfile, add a section named yate to the data object passed into grunt.initConfig().

grunt.initConfig({
  yate: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
})

Options

options.iife

Type: Boolean Default value: true

Wrap the compiled templates into IIFE.

options.runtime

Type: Boolean Default value: true

Prepend destination file with runtime.js library from yate.

options.postprocess

Type: Function

Define compiled code transformations. For instance, one can create autorunning templates:

grunt.initConfig({
  yate: {
    options: {
      postprocess: function(code) {
        // Autorun the `main` module.
        return code + '\nreturn function(data) { return yr.run("main", data); };';
      }
    }
    // ...
  }
});

Usage Examples

When using default options each destination file is wrapped into IIFE and prepended by runtime.js.

Compile single file:

grunt.initConfig({
  yate: {
    options: {},
    files: {
      'templates/compiled/index.js': [
        'templates/src/index.yate',
        'templates/src/blocks/*.yate'
      ]
    }
  }
});

Compile multiple files, using one-to-one mapping:

grunt.initConfig({
  yate: {
    options: {
      runtime: false
    },
    files: [
      {
        dest: 'templates/compiled/',
        src: 'templates/src/*.yate',
        ext: '.js',
        expand: true,
        flatten: true
      }
    ]
  }
});

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

(Nothing yet)