ejs vs handlebars vs mustache vs pug vs nunjucks vs liquidjs vs twig
Template Engines for Web Development Comparison
1 Year
ejshandlebarsmustachepugnunjucksliquidjstwig
What's Template Engines for Web Development?

Template engines are tools that allow developers to generate HTML dynamically by embedding data into templates. They help separate the presentation layer from the business logic, making it easier to manage and maintain web applications. Each of these template engines has its unique syntax and features, catering to different use cases and developer preferences. They facilitate the rendering of views in web applications, enabling developers to create dynamic and interactive user interfaces efficiently.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
ejs19,944,6817,854143 kB11110 months agoApache-2.0
handlebars16,514,51918,1352.78 MB992 years agoMIT
mustache5,867,18516,578-1144 years agoMIT
pug1,651,215-59.7 kB-9 months agoMIT
nunjucks982,7558,6361.77 MB3422 years agoBSD-2-Clause
liquidjs557,9021,5971.76 MB33 days agoMIT
twig313,3861,8981.17 MB65a year agoBSD-2-Clause
Feature Comparison: ejs vs handlebars vs mustache vs pug vs nunjucks vs liquidjs vs twig

Syntax

  • ejs:

    EJS uses plain HTML with embedded JavaScript, making it easy for developers familiar with HTML to get started. It allows for inline JavaScript execution, which can be both a strength and a weakness depending on the use case.

  • handlebars:

    Handlebars employs a more structured syntax with placeholders and expressions, promoting a clean separation between HTML and logic. It avoids inline JavaScript, which can lead to cleaner templates.

  • mustache:

    Mustache uses a minimalistic syntax with curly braces for placeholders, focusing on simplicity and logic-less templates. This makes it easy to understand but limits dynamic capabilities.

  • pug:

    Pug uses an indentation-based syntax that eliminates the need for closing tags, resulting in cleaner and more concise code. Its unique syntax can have a learning curve but enhances readability.

  • nunjucks:

    Nunjucks combines a familiar syntax similar to Jinja2, allowing for template inheritance and blocks. This makes it powerful for creating complex layouts while maintaining readability.

  • liquidjs:

    LiquidJS features a simple syntax with tags, filters, and objects, designed to be safe and secure. It is easy to read and write, making it user-friendly for non-developers as well.

  • twig:

    Twig employs a syntax that is both expressive and powerful, with features like filters and functions. It is designed to be intuitive for developers, especially those familiar with PHP.

Features

  • ejs:

    EJS supports partials, includes, and basic logic, making it suitable for simple applications. However, it lacks more advanced features like template inheritance.

  • handlebars:

    Handlebars offers advanced features like helpers, partials, and built-in support for custom helpers, making it ideal for larger applications that require reusable components.

  • mustache:

    Mustache is intentionally logic-less, focusing on simplicity. It supports basic features like sections and inverted sections but lacks advanced capabilities like inheritance.

  • pug:

    Pug supports mixins, inheritance, and includes, allowing for modular and reusable templates. Its features enhance productivity and maintainability in larger projects.

  • nunjucks:

    Nunjucks includes powerful features such as template inheritance, asynchronous rendering, and custom filters, making it suitable for complex applications.

  • liquidjs:

    LiquidJS provides a secure environment with built-in filters and tags, making it suitable for user-generated content. It also supports custom filters for added flexibility.

  • twig:

    Twig provides a rich set of features, including template inheritance, filters, and macros, making it a powerful choice for complex applications that require a robust templating solution.

Performance

  • ejs:

    EJS is lightweight and performs well for small to medium-sized applications. However, performance may degrade with complex logic embedded in templates due to its inline JavaScript execution.

  • handlebars:

    Handlebars is optimized for performance, especially with precompiled templates. It is efficient for larger applications with reusable components, as it minimizes the amount of logic in templates.

  • mustache:

    Mustache is lightweight and performs well due to its minimalistic design. However, its lack of advanced features may limit performance in complex scenarios.

  • pug:

    Pug is designed for performance with its indentation-based syntax, which reduces the amount of code to parse. However, performance can be impacted by complex mixins and includes.

  • nunjucks:

    Nunjucks can handle complex templates efficiently, but performance may vary depending on the use of asynchronous rendering. It is generally performant for large applications.

  • liquidjs:

    LiquidJS is designed for performance and security, making it suitable for applications that require safe rendering of user-generated content. Its performance is generally good for most use cases.

  • twig:

    Twig is optimized for performance, especially in PHP environments. Its caching mechanism enhances performance for applications with many templates.

Community and Ecosystem

  • ejs:

    EJS has a strong community and is widely used in the Node.js ecosystem, making it easy to find resources and support. However, it may lack some advanced features compared to others.

  • handlebars:

    Handlebars has a vibrant community and a rich ecosystem of extensions and helpers, providing ample resources for developers. It is widely adopted in various frameworks and applications.

  • mustache:

    Mustache has a smaller community compared to others but is widely recognized for its simplicity. It is supported in multiple languages, making it versatile but with limited resources.

  • pug:

    Pug has a strong community with extensive documentation and resources available. Its unique syntax has garnered a dedicated user base, especially in the Node.js ecosystem.

  • nunjucks:

    Nunjucks has a supportive community and is well-documented, making it easy to find help and resources. It is increasingly popular for server-side rendering in Node.js applications.

  • liquidjs:

    LiquidJS has a growing community, especially in the context of secure templating for user-generated content. Its ecosystem is expanding with various integrations and plugins.

  • twig:

    Twig has a large and active community, especially in the PHP world. It is well-documented and has a rich ecosystem of plugins and extensions, making it a robust choice for developers.

Learning Curve

  • ejs:

    EJS has a gentle learning curve, especially for those familiar with HTML and JavaScript. Its straightforward syntax makes it easy to pick up and start using quickly.

  • handlebars:

    Handlebars has a moderate learning curve due to its structured syntax and concepts like helpers and partials, but it is generally easy to learn for those with basic templating experience.

  • mustache:

    Mustache is very easy to learn due to its minimalistic design. Its logic-less approach simplifies the learning process for new developers.

  • pug:

    Pug has a steeper learning curve due to its unique syntax and indentation-based structure. However, once learned, it can significantly enhance productivity and code readability.

  • nunjucks:

    Nunjucks has a moderate learning curve, especially for those familiar with other templating engines. Its advanced features may require some time to master, but it is generally approachable.

  • liquidjs:

    LiquidJS is user-friendly and has a low learning curve, making it accessible for non-developers. Its syntax is intuitive, allowing users to create templates without extensive coding knowledge.

  • twig:

    Twig has a moderate learning curve, especially for developers familiar with PHP. Its expressive syntax and rich feature set may take some time to master, but it is generally intuitive.

How to Choose: ejs vs handlebars vs mustache vs pug vs nunjucks vs liquidjs vs twig
  • ejs:

    Choose EJS if you need a simple and straightforward templating engine that allows you to embed JavaScript directly into your HTML. It is lightweight and easy to integrate with Express.js applications.

  • handlebars:

    Select Handlebars if you prefer a logic-less templating approach that emphasizes separation of concerns. It supports helpers and partials, making it suitable for larger applications requiring reusable templates.

  • mustache:

    Use Mustache if you need a minimalistic and logic-less templating engine that can be used across different programming languages. Its simplicity makes it easy to learn and implement in various projects.

  • pug:

    Select Pug if you want a clean and concise syntax that reduces the amount of HTML code you write. Its indentation-based structure can improve readability and maintainability, especially in large projects.

  • nunjucks:

    Choose Nunjucks if you need a powerful templating engine with advanced features like template inheritance and asynchronous control. It is well-suited for complex applications requiring a robust templating solution.

  • liquidjs:

    Opt for LiquidJS if you are looking for a secure and flexible templating engine that is designed for safe rendering. It is particularly useful in environments where you want to allow users to create templates without executing arbitrary JavaScript.

  • twig:

    Opt for Twig if you are looking for a flexible and powerful templating engine with a rich feature set, including filters, functions, and template inheritance. It is particularly popular in PHP applications but can also be used in Node.js.

README for ejs

Embedded JavaScript templates
Known Vulnerabilities

Security

Security professionals, before reporting any security issues, please reference the SECURITY.md in this project, in particular, the following: "EJS is effectively a JavaScript runtime. Its entire job is to execute JavaScript. If you run the EJS render method without checking the inputs yourself, you are responsible for the results."

In short, DO NOT submit 'vulnerabilities' that include this snippet of code:

app.get('/', (req, res) => {
  res.render('index', req.query);
});

Installation

$ npm install ejs

Features

  • Control flow with <% %>
  • Escaped output with <%= %> (escape function configurable)
  • Unescaped raw output with <%- %>
  • Newline-trim mode ('newline slurping') with -%> ending tag
  • Whitespace-trim mode (slurp all whitespace) for control flow with <%_ _%>
  • Custom delimiters (e.g. [? ?] instead of <% %>)
  • Includes
  • Client-side support
  • Static caching of intermediate JavaScript
  • Static caching of templates
  • Complies with the Express view system

Example

<% if (user) { %>
  <h2><%= user.name %></h2>
<% } %>

Try EJS online at: https://ionicabizau.github.io/ejs-playground/.

Basic usage

let template = ejs.compile(str, options);
template(data);
// => Rendered HTML string

ejs.render(str, data, options);
// => Rendered HTML string

ejs.renderFile(filename, data, options, function(err, str){
    // str => Rendered HTML string
});

It is also possible to use ejs.render(dataAndOptions); where you pass everything in a single object. In that case, you'll end up with local variables for all the passed options. However, be aware that your code could break if we add an option with the same name as one of your data object's properties. Therefore, we do not recommend using this shortcut.

Important

You should never give end-users unfettered access to the EJS render method, If you do so you are using EJS in an inherently un-secure way.

Options

  • cache Compiled functions are cached, requires filename
  • filename The name of the file being rendered. Not required if you are using renderFile(). Used by cache to key caches, and for includes.
  • root Set template root(s) for includes with an absolute path (e.g, /file.ejs). Can be array to try to resolve include from multiple directories.
  • views An array of paths to use when resolving includes with relative paths.
  • context Function execution context
  • compileDebug When false no debug instrumentation is compiled
  • client When true, compiles a function that can be rendered in the browser without needing to load the EJS Runtime (ejs.min.js).
  • delimiter Character to use for inner delimiter, by default '%'
  • openDelimiter Character to use for opening delimiter, by default '<'
  • closeDelimiter Character to use for closing delimiter, by default '>'
  • debug Outputs generated function body
  • strict When set to true, generated function is in strict mode
  • _with Whether or not to use with() {} constructs. If false then the locals will be stored in the locals object. Set to false in strict mode.
  • destructuredLocals An array of local variables that are always destructured from the locals object, available even in strict mode.
  • localsName Name to use for the object storing local variables when not using with Defaults to locals
  • rmWhitespace Remove all safe-to-remove whitespace, including leading and trailing whitespace. It also enables a safer version of -%> line slurping for all scriptlet tags (it does not strip new lines of tags in the middle of a line).
  • escape The escaping function used with <%= construct. It is used in rendering and is .toString()ed in the generation of client functions. (By default escapes XML).
  • outputFunctionName Set to a string (e.g., 'echo' or 'print') for a function to print output inside scriptlet tags.
  • async When true, EJS will use an async function for rendering. (Depends on async/await support in the JS runtime.
  • includer Custom function to handle EJS includes, receives (originalPath, parsedPath) parameters, where originalPath is the path in include as-is and parsedPath is the previously resolved path. Should return an object { filename, template }, you may return only one of the properties, where filename is the final parsed path and template is the included content.

This project uses JSDoc. For the full public API documentation, clone the repository and run jake doc. This will run JSDoc with the proper options and output the documentation to out/. If you want the both the public & private API docs, run jake devdoc instead.

Tags

  • <% 'Scriptlet' tag, for control-flow, no output
  • <%_ 'Whitespace Slurping' Scriptlet tag, strips all whitespace before it
  • <%= Outputs the value into the template (escaped)
  • <%- Outputs the unescaped value into the template
  • <%# Comment tag, no execution, no output
  • <%% Outputs a literal '<%'
  • %%> Outputs a literal '%>'
  • %> Plain ending tag
  • -%> Trim-mode ('newline slurp') tag, trims following newline
  • _%> 'Whitespace Slurping' ending tag, removes all whitespace after it

For the full syntax documentation, please see docs/syntax.md.

Includes

Includes either have to be an absolute path, or, if not, are assumed as relative to the template with the include call. For example if you are including ./views/user/show.ejs from ./views/users.ejs you would use <%- include('user/show') %>.

You must specify the filename option for the template with the include call unless you are using renderFile().

You'll likely want to use the raw output tag (<%-) with your include to avoid double-escaping the HTML output.

<ul>
  <% users.forEach(function(user){ %>
    <%- include('user/show', {user: user}) %>
  <% }); %>
</ul>

Includes are inserted at runtime, so you can use variables for the path in the include call (for example <%- include(somePath) %>). Variables in your top-level data object are available to all your includes, but local variables need to be passed down.

NOTE: Include preprocessor directives (<% include user/show %>) are not supported in v3.0+.

Custom delimiters

Custom delimiters can be applied on a per-template basis, or globally:

let ejs = require('ejs'),
    users = ['geddy', 'neil', 'alex'];

// Just one template
ejs.render('<p>[?= users.join(" | "); ?]</p>', {users: users}, {delimiter: '?', openDelimiter: '[', closeDelimiter: ']'});
// => '<p>geddy | neil | alex</p>'

// Or globally
ejs.delimiter = '?';
ejs.openDelimiter = '[';
ejs.closeDelimiter = ']';
ejs.render('<p>[?= users.join(" | "); ?]</p>', {users: users});
// => '<p>geddy | neil | alex</p>'

Caching

EJS ships with a basic in-process cache for caching the intermediate JavaScript functions used to render templates. It's easy to plug in LRU caching using Node's lru-cache library:

let ejs = require('ejs'),
    LRU = require('lru-cache');
ejs.cache = LRU(100); // LRU cache with 100-item limit

If you want to clear the EJS cache, call ejs.clearCache. If you're using the LRU cache and need a different limit, simple reset ejs.cache to a new instance of the LRU.

Custom file loader

The default file loader is fs.readFileSync, if you want to customize it, you can set ejs.fileLoader.

let ejs = require('ejs');
let myFileLoad = function (filePath) {
  return 'myFileLoad: ' + fs.readFileSync(filePath);
};

ejs.fileLoader = myFileLoad;

With this feature, you can preprocess the template before reading it.

Layouts

EJS does not specifically support blocks, but layouts can be implemented by including headers and footers, like so:

<%- include('header') -%>
<h1>
  Title
</h1>
<p>
  My page
</p>
<%- include('footer') -%>

Client-side support

Go to the Latest Release, download ./ejs.js or ./ejs.min.js. Alternately, you can compile it yourself by cloning the repository and running jake build (or $(npm bin)/jake build if jake is not installed globally).

Include one of these files on your page, and ejs should be available globally.

Example

<div id="output"></div>
<script src="ejs.min.js"></script>
<script>
  let people = ['geddy', 'neil', 'alex'],
      html = ejs.render('<%= people.join(", "); %>', {people: people});
  // With jQuery:
  $('#output').html(html);
  // Vanilla JS:
  document.getElementById('output').innerHTML = html;
</script>

Caveats

Most of EJS will work as expected; however, there are a few things to note:

  1. Obviously, since you do not have access to the filesystem, ejs.renderFile() won't work.
  2. For the same reason, includes do not work unless you use an include callback. Here is an example:
let str = "Hello <%= include('file', {person: 'John'}); %>",
    fn = ejs.compile(str, {client: true});

fn(data, null, function(path, d){ // include callback
  // path -> 'file'
  // d -> {person: 'John'}
  // Put your code here
  // Return the contents of file as a string
}); // returns rendered string

See the examples folder for more details.

CLI

EJS ships with a full-featured CLI. Options are similar to those used in JavaScript code:

  • -o / --output-file FILE Write the rendered output to FILE rather than stdout.
  • -f / --data-file FILE Must be JSON-formatted. Use parsed input from FILE as data for rendering.
  • -i / --data-input STRING Must be JSON-formatted and URI-encoded. Use parsed input from STRING as data for rendering.
  • -m / --delimiter CHARACTER Use CHARACTER with angle brackets for open/close (defaults to %).
  • -p / --open-delimiter CHARACTER Use CHARACTER instead of left angle bracket to open.
  • -c / --close-delimiter CHARACTER Use CHARACTER instead of right angle bracket to close.
  • -s / --strict When set to true, generated function is in strict mode
  • -n / --no-with Use 'locals' object for vars rather than using with (implies --strict).
  • -l / --locals-name Name to use for the object storing local variables when not using with.
  • -w / --rm-whitespace Remove all safe-to-remove whitespace, including leading and trailing whitespace.
  • -d / --debug Outputs generated function body
  • -h / --help Display this help message.
  • -V/v / --version Display the EJS version.

Here are some examples of usage:

$ ejs -p [ -c ] ./template_file.ejs -o ./output.html
$ ejs ./test/fixtures/user.ejs name=Lerxst
$ ejs -n -l _ ./some_template.ejs -f ./data_file.json

Data input

There is a variety of ways to pass the CLI data for rendering.

Stdin:

$ ./test/fixtures/user_data.json | ejs ./test/fixtures/user.ejs
$ ejs ./test/fixtures/user.ejs < test/fixtures/user_data.json

A data file:

$ ejs ./test/fixtures/user.ejs -f ./user_data.json

A command-line option (must be URI-encoded):

./bin/cli.js -i %7B%22name%22%3A%20%22foo%22%7D ./test/fixtures/user.ejs

Or, passing values directly at the end of the invocation:

./bin/cli.js -m $ ./test/fixtures/user.ejs name=foo

Output

The CLI by default send output to stdout, but you can use the -o or --output-file flag to specify a target file to send the output to.

IDE Integration with Syntax Highlighting

VSCode:Javascript EJS by DigitalBrainstem

Related projects

There are a number of implementations of EJS:

  • TJ's implementation, the v1 of this library: https://github.com/tj/ejs
  • EJS Embedded JavaScript Framework on Google Code: https://code.google.com/p/embeddedjavascript/
  • Sam Stephenson's Ruby implementation: https://rubygems.org/gems/ejs
  • Erubis, an ERB implementation which also runs JavaScript: http://www.kuwata-lab.com/erubis/users-guide.04.html#lang-javascript
  • DigitalBrainstem EJS Language support: https://github.com/Digitalbrainstem/ejs-grammar

License

Licensed under the Apache License, Version 2.0 (http://www.apache.org/licenses/LICENSE-2.0)


EJS Embedded JavaScript templates copyright 2112 mde@fleegix.org.