Temper compiles template for client and server side usage.
The following template engines are supported:
As you can see from the list above, we support multiple version engines for the
mustache extension. You can supply your preference through the API. If no
preference is given it will iterate over the template engines and the one that
is successfully required will be used automatically.
Temper is distributed through npm:
npm install --save temper
Temper doesn't depend on any template engines so you need to install these your
self. For these examples I'm going to assume that you have
jade installed as
template engine. Run
npm install --save jade if this is not the case.
Initialising temper is quite simple:
'use strict';var Temper = require'temper'temper = ;
Temper constructor allows the following options:
cacheshould we cache the compiled template, this defaults to
NODE_ENVis set to
production. You usually want to have this disabled during development so you can see the changes in your template without having to restart your node process.
The following methods can be used to interact with
temper.fetch method allows you to pre-compile your template file. This
is advised as requiring modules and reading files is done synchronous. Simply
call this method with a file location and an option engine argument.
Temper will try it's best to automatically discover template engines based on
file extensions, but sometimes this is impossible. There are tons of
compatible template engines and we cannot figure out which one you want based on
the extension. But for template languages such as
jade it's quite simple.
var data = temperprefetch'/file/path/to/template.jade';var data = temperprefetch'/file/path/to/template.mustache' 'hogan.js';
The resulting compiled template have a uniform interface. It's a function that accepts the template data as first argument and returns the generated template.
var template = temperfetch'/file/path/to/template.jade'html = template foo: 'bar' ;console.loghtml;