Bump mustache from 0.7.3 to 4.0.1 in /html5_presentation/reveal.js

Open dependabot[bot] opened this issue 5 years ago • 1 comments

Bumps mustache from 0.7.3 to 4.0.1.

Release notes

v3.1.0

Added

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

Fixed

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

#716: janl/mustache.js#716 #717: janl/mustache.js#717 [@JEStaubach]: https://github.com/JEStaubach [@yotammadem]: https://github.com/yotammadem

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.

v3.0.1

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

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

... (truncated)

Changelog

Sourced from mustache's changelog.

[4.0.1] / 15 March 2020

Fixed

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

[4.0.0] / 16 January 2020

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

... (truncated)

Commits

1de94bb :ship: bump to version 4.0.1
f3bd888 Fix custom delimiters in nested partials (#739)
aca97b8 :ship: bump to version 4.0.0
f3012a2 Remove mustache.to_html() (#735)
5938104 Use fetched template in usage example
3bdd27c Add a section about TypeScript defs in README
7f94f13 Move CLI and contribute section down in README
39ee6ff Point out it's a zero-dependency package in README
c41045b Removing the rtype API definitions from README
bd742d5 Add response.text() from fetch() in README example
Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by flipp, a new releaser for mustache since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
@dependabot use these labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Apr 18 '20 15:04 dependabot[bot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

Dec 31 '20 09:12 dependabot[bot]