fix(deps): update dependency mustache to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
mustache	~2.2.1 -> ~4.2.0
mustache	2.3.0 -> 4.2.0

---

Release Notes

janl/mustache.js (mustache)

v4.2.0

Compare Source

Added

• [#​773]: Add package.json exports field, by [@​manzt].

v4.1.0

Compare Source

Added

• [#​764]: render() now recognizes a config object argument, by [@​pineapplemachine].

Fixed

• [#​764]: Ask custom escape functions to escape all types of values (including numbers), by [@​pineapplemachine].

v4.0.1

Compare Source

Fixed

• [#​739]: Fix custom delimiters in nested partials, by [@​aielo].

v4.0.0

Compare Source

Majority of using projects don't have to worry by this being a new major version.

TLDR; if your project manipulates Writer.prototype.parse | Writer.cache directly or uses .to_html(), you probably have to change that code.

This release allows the internal template cache to be customised, either by disabling it completely
or provide a custom strategy deciding how the cache should behave when mustache.js parses templates.

const mustache = require('mustache');

// disable caching
Mustache.templateCache = undefined;

// or use a built-in Map in modern environments
Mustache.templateCache = new Map();

Projects that wanted to customise the caching behaviour in earlier versions of mustache.js were forced to
override internal method responsible for parsing templates; Writer.prototype.parse. In short, that was unfortunate
because there is more than caching happening in that method.

We've improved that now by introducing a first class API that only affects template caching.

The default template cache behaves as before and is still compatible with older JavaScript environments.
For those who wants to provide a custom more sopisiticated caching strategy, one can do that with an object that adheres to the following requirements:

{
  set(cacheKey: string, value: string): void
  get(cacheKey: string): string | undefined
  clear(): void
}

Added

• [#​731]: Allow template caching to be customised, by [@​AndrewLeedham].

Removed

• [#​735]: Remove .to_html(), by [@​phillipj].

v3.2.1

Compare Source

Fixed

• [#​733]: Allow the CLI to use JavaScript views when the project has ES6 modules enabled, by [@​eobrain].

v3.2.0

Compare Source

Added

• [#​728]: Expose ECMAScript Module in addition to UMD (CommonJS, AMD & global scope), by [@​phillipj] and [@​zekth].

Using mustache.js as an ES module

To stay backwards compatible with already using projects, the default exposed module format is still UMD.
That means projects using mustache.js as an CommonJS, AMD or global scope module, from npm or directly from github.com
can keep on doing that for now.

For those projects who would rather want to use mustache.js as an ES module, the mustache/mustache.mjs file has to
be imported directly.

Below are some usage scenarios for different runtimes.

Modern browser with ES module support

<!-- index.html -->
<script type="module">
  import mustache from "https://unpkg.com/mustache@3.2.0/mustache.mjs"

  console.log(mustache.render('Hello {{name}}!', { name: 'Santa' }))
  // Hello Santa!
</script>

Node.js (>= v13.2.0 or using --experimental-modules flag)

// index.mjs
import mustache from 'mustache/mustache.mjs'

console.log(mustache.render('Hello {{name}}!', { name: 'Santa' }))
// Hello Santa!

ES Module support for Node.js will be improved in the future when Conditional Exports
is enabled by default rather than being behind an experimental flag.

More info in Node.js ECMAScript Modules docs.

Deno

// index.ts
import mustache from 'https://unpkg.com/mustache@3.2.0/mustache.mjs'

console.log(mustache.render('Hello {{name}}!', { name: 'Santa' }))
// Hello Santa!

v3.1.0

Compare Source

Added

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

Fixed

• [#​716]: Bugfix for indentation of inline partials, by [@​yotammadem].

v3.0.3

Compare Source

Added

• [#​713]: Add test cases for custom functions in partials, by [@​wol-soft].

Fixed

• [#​714]: Bugfix for wrong function output in partials with indentation, by [@​phillipj].

v3.0.2

Compare Source

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].

v3.0.1

Compare Source

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

v3.0.0

Compare Source

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.

v2.3.2

Compare Source

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

Minor

• [#​670]: Rollback template cache causing unexpected behaviour, by [@​raymond-lam].

v2.3.1

Compare Source

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

• [#​666]: Install release tools with npm rather than pre-commit hook & Rakefile, by [@​phillipj].
• [#​667], [#​668]: Stabilize browser test suite, by [@​phillipj].

Docs

• [#​644]: Document global Mustache.escape overriding capacity, by [@​paultopia].
• [#​657]: Correct Mustache.parse() return type documentation, by [@​bbrooks].

v2.3.0

Compare Source

Minor

• [#​540]: Add optional output argument to mustache CLI, by [@​wizawu].
• [#​597]: Add compatibility with amdclean, by [@​mightyplow].

Dev

• [#​553]: Assert null lookup when rendering an unescaped value, by [@​dasilvacontin].
• [#​580], [#​610]: Ignore eslint for greenkeeper updates, by [@​phillipj].
• [#​560]: Fix CLI tests for Windows, by [@​kookookchoozeus].
• Run browser tests w/node v4, by [@​phillipj].

Docs

• [#​542]: Add API documentation to README, by [@​tomekwi].
• [#​546]: Add missing syntax highlighting to README code blocks, by [@​pra85].
• [#​569]: Update Ctemplate links in README, by [@​mortonfox].
• [#​592]: Change "loadUser" to "loadUser()" in README, by [@​Flaque].
• [#​593]: Adding doctype to HTML code example in README, by [@​calvinf].

Dependencies

• eslint -> 2.2.0. Breaking changes fix by [@​phillipj]. [#​548]
• eslint -> 2.5.1.
• mocha -> 3.0.2.
• zuul -> 3.11.0.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.