Skip to content

@phillipj phillipj released this Sep 13, 2019 · 34 commits to master since this release

Added

  • #717: Added support .js files as views in command line tool, by @JEStaubach.

Fixed

Assets 2
Aug 27, 2019
🚢 bump to version 3.0.3

@phillipj phillipj released this Aug 21, 2019 · 41 commits to master since this release

Fixed

Dev

  • #701: Fix test failure for Node 10 and above, by @andersk.
  • #704: Lint all test files just like the source files, by @phillipj.
  • Start experimenting & comparing GitHub Actions vs Travis CI, by @phillipj.
Assets 2

@phillipj phillipj released this Nov 11, 2018 · 56 commits to master since this release

#679: Fix partials not rendering tokens when using custom tags, by @stackchain.

Assets 2

@phillipj phillipj released this Sep 16, 2018 · 60 commits to master since this release

3.0.0 / 16 September 2018

We are very happy to announce a new major version of mustache.js. We want to be very careful not to break projects out in the wild, and adhering to Semantic Versioning we have therefore cut this new major version.

The changes introduced will likely not require any actions for most using projects. The things to look out
for that might cause unexpected rendering results are described in the migration guide below.

A big shout out and thanks to @raymond-lam for this release! Without his contributions with code and
issue triaging, this release would never have happened.

Major

  • #618: Allow rendering properties of primitive types that are not objects, by @raymond-lam.
  • #643: Writer.prototype.parse to cache by tags in addition to template string, by @raymond-lam.
  • #664: Fix Writer.prototype.parse cache, by @seminaoki.

Minor

Migrating from mustache.js v2.x to v3.x

Rendering properties of primitive types

We have ensured properties of primitive types can be rendered at all times. That means Array.length, String.length and similar. A corner case where this could cause unexpected output follows:

View:

{
  stooges: [
    { name: "Moe" },
    { name: "Larry" },
    { name: "Curly" }
  ]
}

Template:

{{#stooges}}
  {{name}}: {{name.length}} characters
{{/stooges}}

Output with v3.0:

  Moe: 3 characters
  Larry: 5 characters
  Curly: 5 characters

Output with v2.x:

  Moe:  characters
  Larry:  characters
  Curly:  characters

Caching for templates with custom delimiters

We have improved the templates cache to ensure custom delimiters are taken into consideration for the
cache. This improvement might cause unexpected rendering behaviour for using projects actively using the custom delimiters functionality.

Previously it was possible to use Mustache.parse() as a means to set global custom delimiters. If custom
delimiters were provided as an argument, it would affect all following calls to Mustache.render().
Consider the following:

const template = "[[item.title]] [[item.value]]";
mustache.parse(template, ["[[", "]]"]);

console.log(
  mustache.render(template, {
    item: {
      title: "TEST",
      value: 1
    }
  })
);

>> TEST 1

The above illustrates the fact that Mustache.parse() made mustache.js cache the template without
considering the custom delimiters provided. This is no longer true.

We no longer encourage using Mustache.parse() for this purpose, but have rather added a fourth argument to Mustache.render() letting you provide custom delimiters when rendering.

If you still need the pre-parse the template and use custom delimiters at the same time, ensure to provide
the custom delimiters as argument to Mustache.render() as well.

Assets 2

@phillipj phillipj released this Aug 17, 2018 · 67 commits to master since this release

This release is made to revert changes introduced in 2.3.1 that caused unexpected behaviour for several users.

Minor

Assets 2

@phillipj phillipj released this Aug 7, 2018 · 70 commits to master since this release

Minor

  • #643: Writer.prototype.parse to cache by tags in addition to template string, by @raymond-lam.
  • #664: Fix Writer.prototype.parse cache, by @seminaoki.

Dev

Docs

  • #644: Document global Mustache.escape overriding capacity, by @paultopia.
  • #657: Correct Mustache.parse() return type documentation, by @bbrooks.
Assets 2
You can’t perform that action at this time.