Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

node-barefoot

swissmanu6MIT0.0.11

Barefoot makes code sharing between browser and server reality. Write your application once and run it on both ends of the wire.

backbone, node, server, http, shared

readme

Barefoot

Barefoot makes code sharing between browser and server reality. Write your application once and run it on both ends of the wire.

It builds upon the popular Backbone.JS library and keeps its own additions as unobtrusive as possible.

Server side execution is accomplished by using Node.JS and Express.JS. Once delivered to the users browser, no additional JavaScript libraries are needed when configured properly.

If you implement your views with care, your application will match the Unobtrusive JavaScript principle completely.

Build Status Coverage Status

Installation

npm install node-barefoot

Documentation

The latest version of the code documenation is available here:

To generate a set of documentation locally, make sure you have NaturalDocs installed on your system. To build the documentation into the docs subdirectory, simply run make docs on your command line.

Bitdeli Badge

changelog

Changes

0.0.11

  • Don't start Backbone.History for browsers not supporting JavaScript History and/or pushState

0.0.10

  • Bug fixed: DataStore was not deserializing collections properly.

0.0.9

  • APIAdapter.Server provides the del alias for delete now to ensure compatibility with JavaScripts reserved words.

0.0.8

  • Introduction of Debug for code flow analysis. Thx @mweibel :)

0.0.7

  • Introduced promises for rendering Views using Q
    • The beforeRender and afterRender hook has a resolve and reject argument now. These make it possible to wait for asynchronous function calls. Perfect for populating models with data from the APIAdapter before proceed with the actual rendering.

0.0.6

  • APIAdapter.Server uses winston for logging errors now
  • APIAdapter.Server does not crash anymore if an error callback does not supply an error object as argument
  • APIAdapter.Server forwards the error message to the REST HTTP client for easier bug tracking

0.0.5

  • Stack multiple callbacks to an APIAdapter route. Call success to proceed with the next callback, call error to stop the execution of any further callback.