9.0 KiB
Consolidate.js
Template engine consolidation library.
Installation
$ npm install consolidate
Supported template engines
- atpl
- bracket
- doT.js (website)
- dust (unmaintained) (website)
- dustjs-linkedin (maintained fork of dust) (website)
- eco
- ect (website)
- ejs (website)
- haml
- haml-coffee
- hamlet
- handlebars (website)
- hogan (website)
- htmling
- jade (website)
- jazz
- jqtpl
- JUST
- liquor
- lodash (website)
- marko (website)
- mote (website)
- mustache
- nunjucks (website)
- plates
- pug (formerly jade) (website)
- QEJS
- ractive
- react
- slm
- swig (unmaintained)
- swig (maintained fork)
- teacup
- templayed
- twig
- liquid (website)
- toffee
- underscore (website)
- vash
- walrus (website)
- whiskers
NOTE: you must still install the engines you wish to use, add them to your package.json dependencies.
API
All templates supported by this library may be rendered using the
signature (path[, locals], callback)
as shown below, which
happens to be the signature that Express 3.x supports so any of these
engines may be used within Express.
NOTE: All this example code uses cons.swig for the
swig template engine. Replace swig with whatever templating you are
using. For example, use cons.hogan for hogan.js, cons.jade for jade,
etc. console.log(cons)
for the full list of
identifiers.
var cons = require('consolidate');
.swig('views/page.html', { user: 'tobi' }, function(err, html){
consif (err) throw err;
console.log(html);
; })
Or without options / local variables:
var cons = require('consolidate');
.swig('views/page.html', function(err, html){
consif (err) throw err;
console.log(html);
; })
To dynamically pass the engine, simply use the subscript operator and a variable:
var cons = require('consolidate')
, name = 'swig';
'views/page.html', { user: 'tobi' }, function(err, html){
cons[name](if (err) throw err;
console.log(html);
; })
Promises
Additionally, all templates optionally return a promise if no
callback function is provided. The promise represents the eventual
result of the template function which will either resolve to a string,
compiled from the template, or be rejected. Promises expose a
then
method which registers callbacks to receive the
promise’s eventual value and a catch
method which the
reason why the promise could not be fulfilled. Promises allow more
synchronous-like code structure and solve issues like race
conditions.
var cons = require('consolidate');
.swig('views/page.html', { user: 'tobi' })
cons.then(function (html) {
console.log(html);
}).catch(function (err) {
throw err;
; })
Caching
To enable caching simply pass { cache: true }
. Engines
may use this option to cache things reading the file contents,
compiled Function
s etc. Engines which do not
support this may simply ignore it. All engines that consolidate.js
implements I/O for will cache the file contents, ideal for production
environments. When using consolidate directly:
cons.swig('views/page.html', { user: 'tobi', cache:true }, callback);
Using Express 3 or higher: app.locals.cache = true
or set
NODE_ENV to ‘production’ and Express will do this for you.
Express 3.x example
var express = require('express')
, cons = require('consolidate')
, app = express();
// assign the swig engine to .html files
.engine('html', cons.swig);
app
// set .html as the default extension
.set('view engine', 'html');
app.set('views', __dirname + '/views');
app
var users = [];
.push({ name: 'tobi' });
users.push({ name: 'loki' });
users.push({ name: 'jane' });
users
.get('/', function(req, res){
app.render('index', {
restitle: 'Consolidate.js'
;
});
})
.get('/users', function(req, res){
app.render('users', {
restitle: 'Users',
users: users
;
});
})
.listen(3000);
appconsole.log('Express server listening on port 3000');
Template Engine Instances
Template engines are exposed via the cons.requires
object, but they are not instantiated until you’ve called the
cons[engine].render()
method. You can instantiate them
manually beforehand if you want to add filters, globals, mixins, or
other engine features.
var cons = require('consolidate'),
= require('nunjucks');
nunjucks
// add nunjucks to requires so filters can be
// added and the same instance will be used inside the render method
.requires.nunjucks = nunjucks.configure();
cons
.requires.nunjucks.addFilter('foo', function () {
consreturn 'bar';
; })
Notes
- If you’re using Nunjucks, please take a look at the
exports.nunjucks.render
function inlib.consolidate.js
. You can pass your own engine/environment viaoptions.nunjucksEnv
, or if you want to support Express you can passoptions.settings.views
, or if you have another use case, passoptions.nunjucks
(see the code for more insight). - You can pass partials with
options.partials
- For using template inheritance with nunjucks, you
can pass a loader with
options.loader
. - To use filters with tinyliquid, use
options.filters
and specify an array of properties, each of which is a named filter function. A filter function takes a string as a parameter and returns a modified version of it. - To use custom tags with tinyliquid, use
options.customTags
to specify an array of tag functions that follow the tinyliquid custom tag definition. - The default directory used with the include tag
with tinyliquid is the current working directory. To override this, use
options.includeDir
. React
To render content into a html base template (eg.index.html
of your React app), pass the path of the template withoptions.base
.
Running tests
Install dev deps:
$ npm install -d
Run the tests:
$ make test
License
(The MIT License)
Copyright (c) 2011-2016 TJ Holowaychuk <tj@vision-media.ca>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ‘Software’), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED ‘AS IS’, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.