[Snyk] Upgrade mustache from 4.1.0 to 4.2.0

[snyk-bot]

Snyk has created this PR to upgrade mustache from 4.1.0 to 4.2.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 3 versions ahead of your current version.
• The recommended version was released 21 days ago, on 2021-03-28.

Release notes

Package name: mustache

• 4.2.0 - 2021-03-28
  

  #773: Add package.json exports field, by @ manzt.

• 4.2.0-beta.0 - 2021-03-14
• 4.1.1-beta.0 - 2021-02-22
• 4.1.0 - 2020-12-05
  

  🚢 bump to version 4.1.0

from mustache GitHub release notes

Commit messages

Package name: mustache

• 813e273 4.2.0
• cc66a70 Preparing CHANGELOG for v4.2.0
• ea3adcf Add package.json `exports` field (#773)
• f15befd Build ESM -> CJS before running tests in browsers via Saucelabs
• 3e29d67 Build ESM -> CJS before running legacy Node.js tests and packaging tests
• 69bf4bd Avoid use of `esm` when running tests on legacy Node.js versions
• d4a5042 Use `esm` package locally when testing to use ESM syntax from CJS code
• a93c39e Bump `mustache.js` version via npm script instead of git pre-commit hook
• 2061046 Remove .min.js from git repository, will be kept in npm package
• cc979e0 Rename .mjs -> .js to make it ESM and not have build output in git
• 9faa18e Remove gitter badge from README.md
• dd74683 Remove nuget.org spec from the repository
• 042fbbe Add separate CI job for linting
• 4dbc88d Extract usage tests into separate GitHub Actions workflow
• a11bfc8 Move Node.js 8 alongside other legacy Node.js versions in CI
• b9e113f Fix GitHub checkout action configuration to pull submodules
• 1ff17aa Include mustache spec tests in CI by checking out submodules
• de09eca Run tests on Node.js 14 & 15 as well
• 36edf68 Only keep Node.js 8 with browser usage tests on Travis CI
• 2502fdf Updated deno usage test to avoid use of deprecated URL

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs