Reactive data binding for web applications.

npm i simulacra --save #v1.2.3 Download Fork on GitHub


Simulacra.js handles the DOM interactions in reaction to changes in data. When data changes, it maps those changes to the DOM by adding and removing elements and invoking change functions, which by default, assign plain text and form input values.

It emphasizes performance and terseness, and it has no dependencies. The approximate size of this library is ~4 KB (minified and gzipped).


Simulacra.js uses plain HTML for templating, and it does not require meta-information in the template at all. Here's a sample template:

<template id="product">
  <h1 class="name"></h1>
  <div class="details">
    <div><span class="size"></span></div>
    <h4 class="vendor"></h4>

Using the <template> tag is optional, but any DOM element will suffice. The shape of the data is important since it has a straightforward mapping to the DOM, and arrays are iterated over to output multiple DOM elements. Here's some sample data:

var data = {
  name: 'Pumpkin Spice Latte',
  details: {
    size: [ 'Tall', 'Grande', 'Venti' ],
    vendor: 'Starbucks'

Simulacra.js exports only a single function, which binds an object to the DOM. The first argument must be a singular object, and the second argument is a data structure that defines the bindings. The definition must be a CSS selector string, DOM Node, change function or definition object (parent binding only), or an array with at most three elements:

var simulacra = require('simulacra') // or `window.simulacra`
var fragment = document.getElementById('product').content

var node = simulacra(data, [ fragment, {
  name: '.name',
  details: [ '.details', {
    size: '.size',
    vendor: '.vendor'
  } ]
} ])


The DOM will update if any of the bound keys are assigned a different value, or if any Array.prototype methods on the value are invoked. Arrays and single values may be used interchangeably, the only difference is that Simulacra.js will iterate over array values.

Here is the result of the example above:

Live demo, try it out:

  • = "Caramel Latte"
  • data.details.size.push("Trenta")
  • data.details.size = [ 'Tall' ]

Change Function#

By default, the value will be assigned to the element's textContent property (or value or checked for inputs). A user-defined change function may be passed for arbitrary element manipulation, and its return value determines the new textContent, value, or checked attribute if it is not applied on a definition object. The change function may be passed as the second or third position, it has the signature (element, value, previousValue, path):

To manipulate an element in a custom way, one may define a change function like so:

[ selector, function (element, value, previousValue) {
  // Attach listeners before inserting a DOM Node.
  if (previousValue === null)
    element.addEventListener('click', function () {

  return 'Hi ' + value + '!'
} ]

A change function can be determined to be an insert, mutate, or remove operation based on whether the value or previous value is null:

There are some special cases for the change function:

State Management#

Since Simulacra.js is intended to be deterministic, the bound object can be cloned at any point in time and bound again to reset to that state. For example, using the clone module:

var clone = require('clone')
var simulacra = require('simulacra')

var data = { ... }, bindings = [ ... ]

var node = simulacra(data, bindings)
var initialData = clone(data)

// Do some mutations, and then reset to initial state.
node = simulacra(initialData, bindings)

This is just one way to implement time travel, but not the most efficient.


Simulacra.js is pretty fast in the DBMonster benchmark. In initial rendering speed based on the benchmarks from Mithril.js, here's how it compares. Tests ran on a Linux desktop using Chromium.

appendChild10 ms3 ms13 ms38 ms
Simulacra.js9 ms9 ms13 ms39 ms
React.js23 ms76 ms13 ms129 ms
Mithril.js16 ms77 ms23 ms165 ms
Backbone20 ms106 ms23 ms191 ms
jQuery20 ms119 ms24 ms211 ms
Angular.js17 ms159 ms24 ms295 ms

To run the benchmarks, you will have to clone the repository and build it by running npm run build. The benchmarks are located here.

How it Works#

On initialization, Simulacra.js replaces bound elements from the template with empty text nodes (markers) for memoizing their positions. Based on a value in the bound data object, it clones template elements and applies the change function on the cloned elements, and appends them near the marker or adjacent nodes.

When a bound key is assigned, it gets internally casted into an array if it is not an array already, and the values of the array are compared with previous values. Based on whether a value at an index has changed, Simulacra.js will remove, insert, or mutate a DOM element corresponding to the value. This is faster and simpler than diffing changes between DOM trees.


Under the Hood#

This library is written in ES5 syntactically, and requires:

It also requires these DOM API features:

No shims are included. At the bare minimum, it works in IE9+ with a WeakMap polyfill, but otherwise it should work in IE11+.

Server-Side Rendering#

Simulacra.js works in Node.js (it's isomorphic!), with one thing to keep in mind: it should be called within the context of the window global, however this may be optional in some implementations. This is most easily done by using Function.prototype.bind, although is more performant. In the following example, Domino is used as the DOM implementation.

const domino = require('domino')
const simulacra = require('simulacra')

const window = domino.createWindow('<h1></h1>')
const $ = simulacra.bind(window)
const data = { message: 'Hello world!' }
const binding = [ 'body', {
  message: 'h1'
} ]

console.log($(data, binding).innerHTML)

This will print the string <h1>Hello world!</h1> to stdout.


This software is licensed under the MIT license.