chore(deps): update dependency mustache to v3.2.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
mustache	3.1.0 -> 3.2.1

---

Release Notes

janl/mustache.js (mustache)

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!

---

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 this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit