This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
chore(deps): update dependency mustache to v4 #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.0.1
->4.2.0
0.8.32
->4.1.2
Release Notes
janl/mustache.js
v4.2.0
Compare Source
Added
exports
field, by [@manzt].v4.1.0
Compare Source
Added
render()
now recognizes a config object argument, by [@pineapplemachine].Fixed
escape
functions to escape all types of values (includingnumber
s), by [@pineapplemachine].v4.0.1
Compare Source
Fixed
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.
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 unfortunatebecause 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:
Added
Removed
.to_html()
, by [@phillipj].v3.2.1
Compare Source
Fixed
v3.2.0
Compare Source
Added
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 tobe
import
ed directly.Below are some usage scenarios for different runtimes.
Modern browser with ES module support
Node.js (>= v13.2.0 or using --experimental-modules flag)
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
v3.1.0
Compare Source
Added
Fixed
v3.0.3
Compare Source
Added
Fixed
v3.0.2
Compare Source
Fixed
Dev
Configuration
📅 Schedule: 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.