handlebars.js v1.1.0 Release Notes
Release Date: 2013-11-03 // over 10 years ago-
- #628 - Convert code to ES6 modules (@kpdecker)
- #336 - Add whitespace control syntax (@kpdecker)
- #535 - Fix for probable JIT error under Safari (@sorentwo)
- #483 - Add first and last @ vars to each helper (@denniskuczynski)
- #557 -
\\{{foo}}
escaping only works in some situations (@dmarcotte) - #552 - Added BOM removal flag. (@blessenm)
๐ #543 - publish passing master builds to s3 (@fivetanley)
#608 - Add
includeZero
flag toif
conditional#498 -
Handlebars.compile
fails on empty string although a single blank works fine#599 - lambda helpers only receive options if used with arguments
๐ #592 - Optimize array and subprogram performance
โฌ๏ธ #571 - uglify upgrade breaks compatibility with older versions of node
#587 - Partial inside partial breaks?
Compatibility notes:
- The project now includes separate artifacts for AMD, CommonJS, and global objects.
- AMD: Users may load the bundled
handlebars.amd.js
orhandlebars.runtime.amd.js
files or load individual modules directly. AMD users should also note that the handlebars object is exposed via thedefault
field on the imported object. This gist provides some discussion of possible compatibility shims. - CommonJS/Node: Node loading occurs as normal via
require
- Globals: The
handlebars.js
andhandlebars.runtime.js
files should behave in the same manner as the v1.0.12 / 1.0.0 release.
- AMD: Users may load the bundled
- ๐ Build artifacts have been removed from the repository. [npm][npm], [components/handlebars.js][components], [cdnjs][cdnjs], or the [builds page][builds-page] should now be used as the source of built artifacts.
- Context-stored helpers are now always passed the
options
hash. Previously no-argument helpers did not have this argument.