Update mustache to the latest version 🚀

greenkeeper[bot] commented 6 years ago

The dependency mustache was updated from `2.3.2` to `3.0.0`.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

Release Notes for v3.0.0

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

#673: Add tags parameter to Mustache.render(), by @raymond-lam.

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.

Commits

The new version differs by 7 commits.

17510f0 :ship: bump to version 3.0.0
f452acb Update v3.0.0 release date in changelog
8ee916a Changelog for v3.0.0 (#674)
a2699e4 Allow rendering properties of primitive types that are not objects (#618)
efdeb55 Add tags parameter to .render()
8e45409 Update README.md to reflect correct caching behavior
7845848 Reintroduce pull requests #643 and #664, and update description for

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper bot :palm_tree:

greenkeeper[bot] commented 5 years ago

The dependency mustache was updated from 2.3.2 to 3.0.1.

Update to this version instead 🚀

Commits

The new version differs by 4 commits.

38b1448 :ship: bump to version 3.0.1
d170f41 Add test to verify custom tags are used in partials for via .render()
b86665d Use older version of eslint to stay pre Node.js 1 compliant a little longer
5a5c1d4 Fix partials not rendering tokens when using custom tags (#678)

See the full diff

greenkeeper[bot] commented 5 years ago

The dependency mustache was updated from 2.3.2 to 3.0.2.

Update to this version instead 🚀

Release Notes for v3.0.2

Fixed

#705: Fix indentation of partials, by @kevindew and @yotammadem.

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.

Commits

The new version differs by 15 commits.

6c3608b :ship: bump to version 3.0.2
619c928 Delete old GitHub Actions workflow file
fc8eb5d Convert to new GitHub Actions yaml format
1c4187a Don't run browser tests on IE 9 and IE 10, start from IE 11 and above
69e2bf3 Add mustache partials indentation spec and fix one broken test
cadf571 Indent Partials
1a244cb Install deps before tests in Actions workflow
930a485 Install deps as part of GitHub Actions workflow
d0290c4 Try a basic GitHub Actions workflow
bb700c5 Start linting all test/ files as part of test script (#704)
11ac71a Run tests on Node.js 10 & 12 after CLI test got fixed
932ad33 cli-test: fs.unlink → fs.unlinkSync to fix test failure on Node 10 (#701)
78eb820 Run tests on Node.js 8 as well
fe06a16 Cut official support for Node.js 0.8 by not running tests on it anymore (#700)
639c94f Updated Beard Competition URL in README.md (#699)