Render views on the server (using standard HTML markup) that the browser can update in realtime when the original data changes.

DEPRECATED! Use rincewind and become instead.
Last updated 6 years ago by mmckegg .
Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install realtime-templates 
SYNC missed versions from official npm registry.

Realtime Templates

Render views on the server (using standard HTML markup) that the browser can update in realtime when the original data changes.

Status: Deprecated

Expect no further updates.

The ideas from this module have been extracted out into more pieces that work a lot better. See rincewind for a similar templating language and become for smooth html-based DOM updates.

Another project tackling a similar problem is mercury by Raynos.

Server API

var http = require('http')

var Renderer = require('realtime-templates')
var JsonContext = require('json-context')

var viewPath = path.join(__dirname, '/views')

// create a renderer - pass in the path containing the HTML views and any options
var renderer = Renderer(viewPath, {includeBindingMetadata: true})

http.createServer(function (req, res) {
  res.writeHead(200, {'Content-Type': 'text/html'});
  // get the data from the database (or in this case, hard coded JSON)
  var datasource = JsonContext({data: {
    title: "Matt's blog",
    element_id: "value",
    type: 'example'
  // render the page and return the result
  renderer.render('page', datasource, function(err, result){
}).listen(1337, '');

require('realtime-templates')(viewPath, options)

The easy way to use Realtime Templates. Pass in the path to a directory containing your HTML views and it returns a template renderer.


  • includeBindingData (defaults false): Whether or not to include data-tx and data-ti attributes on the page to allow realtime updating, and also whether to include the datasource and used views in a script tag at the bottom.
  • formatters: Accepts a hash containing named functions representing a custom method of rendering the html from the original value. See Attribute: t:format.
  • masterName: Pass in the name of a view to use as the overall master layout for all rendered views. Masters must be saved as <masterName>.master.html. See Attribute: t:content

renderer.render(viewName, datasource, callback)

viewName: Specify the name of a view. It will be the filename minus the .html. e.g. For the file page.html the viewName would be page.

datasource: Pass in a datasource object such as JSON Context. The renderer will use this data to put the values into the page.

callback: function(err, result) where result is the final rendered page in HTML. Errors might be returned if the viewName specified doesn't exist, or there was a fatal problem rendering the page.


For custom use - pass in a raw HTML template string and it will be parsed into JSON.

realtimeTemplates.renderView(view, datasource, options)

Pass in a parsed JSON view and a datasource and the function will return an array of RT elements. See Attribute: t:format.


Pass in an array of RT elements and the function returns HTML.

The Templates (data binding, etc)

This module can be used with any datasource object that responds to query and get and emits change events.

However it was designed to be used with JSON Context - a single object that supports querying (using JSON Query) and contains all data required to render a view/page and providing the client with event stream for syncing with server and data-binding to the dom.

See JSON Context for more information about the datasource interface.

Attribute: t:bind

Any time the system hits a t:bind attribute while rendering the view, it sends the value of this attribute to the datasource query function. The return value is inserted as text inside the element.

Attribute: t:bind:<attribute-name>

We can bind arbitrary attributes using the same method by using t:bind:<attribute-name>.

For example, if we wanted to bind an element's ID to element_id in our datasource:

<span t:bind:id='element_id'>content unchanged</span>

Which would output:

<span id='value'>content unchanged</span>

Attribute: t:if

The element will only be rendered if the datasource returns true when queried with the attribute value.

Attribute: t:unless

The inverse of t:if. The element will only be rendered if the datasource does not return true when queried with the attribute value.

Attribute: t:by and t:when

An extension of the if system. Much like a switch or case statement. Specify the source query using t:by then any sub-elements can use t:when to choose what value the t:by query must return in order for them to show. Multiple values may be specified by separating with the pipe symbol (e.g. value1|value2|value3).

<div t:by='type'>
  <div t:when='example'>
    This div is only rendered if the query "type" returns the value "example".
  <div t:when='production'>
    This div is only rendered if the query "type" returns the value "production".
  <div t:when='trick|treat'>
    This div is rendered when the query "type" returns the value "trick" or "treat".

Attribute: t:repeat

For binding to arrays and creating repeating content. The attribute value is queried and the element is duplicated for every item in the returned array.

For this JSON Context datasource:

var datasource = JsonContext({
  posts: [
    {id: 1, title: "Post 1", body: "Here is the body content"},
    {id: 2, title: "Post 2", body: "Here is some more body content"},
    {id: 3, title: "Post 3", body: "We're done."},

And this template:

<div class='post' t:repeat='posts' t:bind:data-id='.id'>
  <h1 t:bind='.title'>Will replaced with the value of title</h1>
  <div t:bind='.body'>Will replaced with the value of body</div>

We would get:

<div class='post' data-id='1'>
  <h1>Post 1</h1>
  <div>Here is the body content</div>
<div class='post' data-id='2'>
  <h1>Post 2</h1>
  <div>Here is some more body content</div>
<div class='post' data-id='3'>
  <h1>Post 3</h1>
  <div>We're done.</div>

If required (e.g. nesting repeaters) you can use t:as to assign the context a name and reference it by that instead of '.'

<div class='post' t:repeat='posts' t:as='post' t:bind:data-id='.id'>
  <div t:repeat='something_else'>
    Can still access the post!
    <span t:bind='' />

Attribute: t:view

Specify a sub-view to render as the content of the element. It must be in the current viewPath in order to be found.

If the element had content specified, it will be overrided with the content of the subview, but if the subview contains an element with the attribute t:content, the removed content will be inserted here. This allows creating views that act like wrappers.

Attribute: t:content

This attribute accepts no value and is used on master views to denote where to insert the actual view content.

Say we have this master layout:

    <title>My Blog</title>
    <h1>My Blog</h1>
    <div t:content id='content'></div>

And this view:

<h2>Page title</h2>
<div>I am the page content</div>

We would get:

    <title>My Blog</title>
    <h1>My Blog</h1>
    <div id='content'> <!--inner view is inserted here--> 
      <h2>Page title</h2>
      <div>I am the page content</div>

Attribute: t:format

This attribute is used to specify a custom renderer to use for rendering the value of t:bind. It could be used to apply Markdown or Textile to the original text.

Formatters are functions that except a value parameter and return an array of elements in RT format. The RT format looks something like this:

// [tag, attributes, sub-elements]
['div', {id: 'content'}, [
  ['h2', {}, [
    {text: 'Page title'}
  ['div', {}, [
    {text: 'I am the page content'}

Formatters are specified when creating the RT renderer. This example formatter replaces new lines with <br/> tags:

function formatMultiLine(input){
  var result = []
  input.split('\n').forEach(function(line, i){
    if (i > 0){
      result.push(['br', {}, []])
    result.push({text: line})
  return result

var renderer = Renderer(viewPath, {
  includeBindingMetadata: true, 
  formatters: {
    multiline: formatMultiLine //specify the function we created above as a formatter

Making it realtime

After the page is loaded in the browser, the system scans for meta tags (data-tx and data-ti) added by the renderer to figure out what every thing is. It queries the datasource and creates a two way reference between the original object and the element that represents that object.

Then it listens for change events on the datasource, using the two way reference to figure out what needs to change, or if it needs to add a new element or remove an existing one.

Using it with JSON Context

With JSON Context, rather than updating objects directly, we use change streams to push new or changed objects in. This means we have to tell the context how to handle the various changes that could be piped in. It makes sense to have the this map directly to our database 1:1. We do this using matchers.

We also need a way to identify each object that will need to be changed. Since we made the matchers correspond to our database objects, we can use the unique ID provided by the database.

Say we have the following context:

  posts: [
    {id: 1, type: 'post', title: "Post 1", body: "Here is the body content"},
    {id: 2, type: 'post', title: "Post 2", body: "Here is some more body content"},
    {id: 3, type: 'post', title: "Post 3", body: "We're done."},
  comments: {
    '2': [
      {id: 1, post_id: 2, type: 'comment', name: 'Anonymous Coward' text: "This is dumb"},
      {id: 2, post_id: 2, type: 'comment', name: 'Bill Gates', text: "wish i thought of this!"}
  } // We have grouped/indexed the comments by post_id as this is how they will be most commonly accessed.

If we wanted to be able to add comments in realtime, we would add the following matcher:

  match: {type: 'comment'}, // we apply the rule if the incoming object has the type 'comment'
  allow: {
    append: true
  item: 'comments[][id={.id}]', // a JSON Query that finds the comment so it can be updated
  collection: 'comments[{.post_id}]' // a JSON Query that specifies where append new items

When the includeBindingMetadata option is enabled, the renderer automatically appends a script tag to the output (with type='text/json' so it won't execute) that contains a full copy of the datasource and the templates used to render it. We can pull that data in and recreate the context in the browser

// client-side require using browserify
var JsonContext = require('json-context')

var bindingElement = document.getElementById('realtimeBindingInfo')
var meta = JSON.parse(bindingElement.innerHTML)

window.context = JsonContext({data:, matchers: meta.matchers})

Now we just need to subscribe to the server's change feed. The server will send us the new object, and the matchers are used to figure out if we care and where to update if we do.

  // client-side require using browserify
  var Shoe = require('shoe')

  var clientStream = window.context.changeStream({verifiedChange: true})
  var serverStream = Shoe('/changes')

Here is the view that we will use:

<div t:repeat='posts'>
  <h2 t:bind='.title'></h2>
  <div t:format='multiline' t:bind='.body'></div>
  <div class='comments'>
    <div t:repeat='comments[{.id}]'>
      <h4 data-bind='.name'></h4>
      <div t:format='multiline' t:bind='.text'></div>

Let's bind it to the datasource

// client-side require using browserify
var realtimeTemplates = require('realtime-templates')

realtimeTemplates.bind(meta.view, window.context)

Now whenever comments are added on the server, they will be updated in realtime in the browser.

The next step is to allow the user to add comments to the page and have these pushed back to the server.

Client API

require('realtime-templates').bind(view, datasource, options)

This must be run in the browser in order for the page to work in realtime.

view: Pass in the parsed view that should be included in a JSON script element with the ID realtimeBindingInfo as view.

datasource: The reconstituted datasource object based on the data included with


  • rootElement (defaults document): A DOM element that corresponds to the root node in the view.
  • formatters: Should be hooked up to the same list of formatters as it's server side counterpart. See Attribute: t:format
  • behaviors: An object containing a list of functions to be run when is extended with data-behavior. See Extending with behaviors

It returns an EventEmitter that emits append, beforeRemove and remove events with a single parameter: node. These can be used to add animation or other hooks.

var jsonContext = require('json-context')
var realtimeTemplates = require('realtime-templates')

var bindingElement = document.getElementById('realtimeBindingInfo')
var meta = JSON.parse(bindingElement.innerHTML)

window.context = jsonContext(, {matchers: meta.matchers})
var binder = realtimeTemplates.bind(meta.view, window.context)

binder.on('append', function(node){
  animations.slideDown(200, node)

binder.on('beforeRemove', function(node, wait){
  // wait is a function that can be called to delay (in milliseconds) the actual removal of the element to allow for an animation.
  animations.slideUp(200, node)

context.pushChange(object, changeInfo)

See JSON Context: pushChange for full details.

Extending with behaviors

data-behaviors attribute

Preserving attributes on Realtime Nodes (element.preserveAttributes)

If you would like to add a class (or change any other attribute on a DOM node) at runtime using Javascript code rather than via binding, you'll need to set the preserveAttributes option to an array containing the attribute names you wish the realtime updating to ignore.

var element = document.getElementById('someElement')
element.preserveAttributes = ['style']

slideUp(element, 200) // the animation will now fire correctly, and 
                      // not get tripped up by attribute reset


  • Testing the browser stuff - maybe with testling or something?
  • Currently preserving elements added at runtime, but would be nice if could also preserve attributes - e.g. additional styles, classes etc.


The server side will run on Node.js.

Mostly cross-browser when using shimify and browserify.

Ruby (and other platforms)

With some clever hacking, RT can be run inside a Ruby project using something like therubyracer.

I am currently running Realtime Templates inside a Ruby on Rails project in production. I used Browserify to generate a package which could be run directly on therubyracer with no dependencies on Node. I do all of the view loading and parsing in the build step and is pulled into the browserify package precompiled. The data is generated in the ruby code and passed off to a function in therubyracer that renders that data into HTML.

It works remarkably well. My plan is eventually to be running 100% on Node.js, but this has helped to get a little bit of Node niceness into my Rails without huge amounts of infrastructure restructuring.

Current Tags

  • 0.3.1                                ...           latest (6 years ago)

9 Versions

  • 0.3.1 [deprecated]           ...           6 years ago
  • 0.3.0 [deprecated]           ...           7 years ago
  • 0.2.4 [deprecated]           ...           7 years ago
  • 0.2.3 [deprecated]           ...           7 years ago
  • 0.2.2 [deprecated]           ...           7 years ago
  • 0.2.1 [deprecated]           ...           7 years ago
  • 0.2.0 [deprecated]           ...           7 years ago
  • 0.1.0 [deprecated]           ...           7 years ago
  • 0.0.0 [deprecated]           ...           7 years ago
Maintainers (1)
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 0
Dependencies (2)
Dev Dependencies (0)
Dependents (1)

Copyright 2014 - 2016 © |