Old school web application library

Usage no npm install needed!

<script type="module">
  import brave from '';



Tiny web application library

Super simple library that helps with building websites.


  • Attaches JS behaviors to DOM elements
  • Backbone-like component definitions
  • jQuery-like like event delegation
  • Angular-like scopes
  • Easy element referencing using aliases
  • Unobtrusive. DOM attribute based selectors
  • Tiny 3K minified/zipped file size

So, what does it do?

  • Allows you to define DOM components using javascript
  • DOM scopes for components that can be isolated or can inherit from their parent
  • Component level event delegation like jQuery live
  • Elements can be aliased onto their scope to avoid document.getElementById calls
<div my-app>
  <h1 as="headingEl"></h1>
  <form my-login="userData" as="formEl">
    <input type="text">
    <input type="password">
    <button as="buttonEl">Login</button>
  <div my-widget="widgetData" as="widgetEl"></div>
  'my-app': {
    initialize: function () {
      this.headingEl.innerHTML =
    showMessage: function (message) {
    sayHi: function () {
      this.showMessage('Hello from app')
    get someProp () {
      return 'I\'m on the the app\'s prototype'
  'my-login': {
    initialize: function () {
    on: {
      'submit:form': function (e) {
    login: function () {
      this.showMessage('Logging in...')
      this.showMessage('I can call my parent scope\'s methods and properties')
  'my-widget': {
    initialize: function () {
    template: function () {
      // This will be rendered when components are initialized.
      // Notice how child components can be created e.g. `my-widget-item`
      var str = '<ul>'
      for (var i = 0; i <; i++) {
        str += '<li my-widget-item="[' + i + ']" as="listItem_' + i + '"></li>'
      str += '</ul>'
      return str
  'my-widget-item': {
    initialize: function () {
    on: {
      click: function (e) {
        this.showMessage('Widget item clicked')
    template: function () {
      return '<a as="item_' + +'" href="#">' + + '</a>'

var data = {
  appName: 'My App',
  userData: {
    userName: 'Jane',
    password: 'secret'
  widgetData: [1, 2, 3]

Brave.scan(document.body, data)

Here's the result of this example

It's enough to start building quite some interesting applications. braves main aim is to application structure by defining web component behaviors allowing you to take control of the DOM.

No two-way binding, or automatic DOM updates are done, how you do this is down to you. There are plenty to options available if you want to use another library alongside or it can just be done the old fashioned way with events. Manually handling DOM updates and managing state yourself can be a chore but there can be lots of benefits over using frameworks in the long run. Building strong models that represent the data on the front end, using a tool like brave to organize and build your controllers/scopes can yield a nice clean code base that's easy to reason about.

brave is not a template library. How you generate HTML is down to you (resigify is used in the Examples). brave works by querying the DOM to look for attributes that match components you have registered. During this query it initializes any components it finds and attaches the behaviors such as events. If a component itself renders some more DOM while initializing, its' new children will then also be processed.

Whilst this processing happens a scope chain of controllers is being built. These are simple JS prototype chains and work in a similar fashion to AngularJS directives in that a components scope can be either isolated or inherit from their parent scope.

If you haven't used Angular before or any of this doesn't make sense don't worry, there's no steep learning curve.

brave works well with both client and server generated HTML, has barely no learning curve and plays well with any other javascript libraries and template engines.

npm install brave --save

var Brave = require('brave')

If you aren't using browserify simply include dist/brave.js in a script tag and it will export window.Brave


An object representing the component. Any custom properties and functions will form part of the scope's prototype. Additionally it can contain the following 4 special properties:


Object map of events.

  on: {
    'click': function (e) {},
    'click:ul li a': function (e) {},
    'submit:form': function (e) {},
    'change:input': function (e) {},

initialize [function]

A function that will be called when the component is being initialized.

template [function|string]

A HTML string or function that returns a HTML string. The function will be passed the current scope. The innerHTML of the element will be set and then scaned.

isolate [boolean(false)]

A Component's scope prototype will inherit from its parent by default. Set this to true and the scope will be isolated.


When a component is initialized a scope is created. That scope will contain on its prototype the custom properties of the component object and any inherited properties (unless it's isolated). A scope will also contain these properties:

  • data - The data object passed in the call to scan
  • render - Can be used for re-rendering. Only present if a template was defined on the component
  • __ - This property holds the component information (isolated, on) etc. Could be useful if you need to reference the component that was used to create the scope.


Used to register a component or components.

Brave.register('name', componentObject) or Brave.register(componentsObject)


  mywidget: {
    on: {
      'click': function (e) {}


Query the DOM for components and initializes them.

Brave.scan(el, [data])

Elements are queried for attributes names matching component name. The value of the attribute can make a reference data. E.g. foo here:

<div mywidget="foo"></div>
var data = {
  foo: {
    bar: 1,
    baz: 2

Brave.scan(document.body, data)


DOM elements can be projected onto their scope by giving them an as attribute

<div mywidget="foo">
  <input as="searchEl" type="text">
  <button as="searchButton" type="button">OK</button>


See the Examples


A similar technique was used by Paul Irish who coined the name DOM based routing