[Snyk] Upgrade mustache from 2.2.1 to 4.0.1 #3
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.
Snyk has created this PR to upgrade mustache from 2.2.1 to 4.0.1.
✨ Snyk has automatically assigned this pull request, set who gets assigned.
ℹ️ 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.
Warning: This is a major version upgrade, and may be a breaking change.
Release notes
Package name: mustache
-
4.0.1 - 2020-03-15
-
4.0.0 - 2020-01-16
-
3.2.1 - 2019-12-30
-
3.2.0 - 2019-12-18
-
3.2.0-beta.0 - 2019-12-07
-
3.1.0 - 2019-09-13
- #717: Added support .js files as views in command line tool, by @ JEStaubach.
- #716: Bugfix for indentation of inline partials, by @ yotammadem.
-
3.0.3 - 2019-08-27
-
3.0.2 - 2019-08-21
- #705: Fix indentation of partials, by @ kevindew and @ yotammadem.
- #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.
-
3.0.1 - 2018-11-11
-
3.0.0 - 2018-09-16
- #618: Allow rendering properties of primitive types that are not objects, by @ raymond-lam.
- #643:
- #664: Fix
- #673: Add
-
2.3.2 - 2018-08-17
- #670: Rollback template cache causing unexpected behaviour, by @ raymond-lam.
-
2.3.1 - 2018-08-07
-
2.3.0 - 2016-11-08
-
2.2.1 - 2015-12-13
from mustache GitHub release notes🚢 bump to version 4.0.1
🚢 bump to version 4.0.0
🚢 bump to version 3.2.1
🚢 bump to version 3.2.0
Added
Fixed
🚢 bump to version 3.0.3
Fixed
Dev
#679: Fix partials not rendering tokens when using custom tags, by @ stackchain.
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
Writer.prototype.parseto cache by tags in addition to template string, by @ raymond-lam.Writer.prototype.parsecache, by @ seminaoki.Minor
tagsparameter toMustache.render(), by @ raymond-lam.Migrating from mustache.js v2.x to v3.x
Rendering properties of primitive types
We have ensured properties of primitive types can be rendered at all times. That means
Array.length,String.lengthand similar. A corner case where this could cause unexpected output follows:View:
Template:
Output with v3.0:
Output with v2.x:
Caching for templates with custom delimiters
We have improved the templates cache to ensure custom delimiters are taken into consideration for the
cache. This improvement might cause unexpected rendering behaviour for using projects actively using the custom delimiters functionality.
Previously it was possible to use
Mustache.parse()as a means to set global custom delimiters. If customdelimiters were provided as an argument, it would affect all following calls to
Mustache.render().Consider the following:
The above illustrates the fact that
Mustache.parse()made mustache.js cache the template withoutconsidering the custom delimiters provided. This is no longer true.
We no longer encourage using
Mustache.parse()for this purpose, but have rather added a fourth argument toMustache.render()letting you provide custom delimiters when rendering.If you still need the pre-parse the template and use custom delimiters at the same time, ensure to provide
the custom delimiters as argument to
Mustache.render()as well.This release is made to revert changes introduced in 2.3.1 that caused unexpected behaviour for several users.
Minor
Commit messages
Package name: mustache
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
👩💻 Set who automatically gets assigned
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs