Bump mustache from 0.7.3 to 3.2.1 in /doc/pub/reveal.js

Open dependabot[bot] opened this issue 6 years ago • 0 comments

Bumps mustache from 0.7.3 to 3.2.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.

[3.2.1] / 30 December 2019

Fixed

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

[3.2.0] / 18 December 2019

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

<script type="module">
  import mustache from "https://unpkg.com/[email protected]/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.
... (truncated)

Commits

8e52a4a :ship: bump to version 3.2.1
aaaa94f Allow JavaScript views to have the .cjs suffix.
70d3e7e :ship: bump to version 3.2.0
492d683 :ship: bump to version 3.2.0-beta.0
f8d7a8d Improve pre-commit hook keeping version in sync to handle beta versions
86fa37d Bump .version in mustache.js in git hook when version has changed
e0a3631 Add CI test verifying native ES Module usage for Node.js
ddad1a7 Add CI test to verify build output is in sync with source (.js vs .mjs)
b72d1a3 Add CI test verifying Mustache works with Deno
c28d73b Make mustache.mjs work with Deno
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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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.

Jan 13 '20 15:01 dependabot[bot]