Releases: mozilla/nunjucks
Releases · mozilla/nunjucks
v1.0.7
v1.0.6
v1.0.5
- Added support for browserify
- Added option to specify template output path when precompiling templates
- Keep version comment in browser minified files
- Speed up SafeString implementation
- Handle null and non-matching cases for word count filter
- Added support for node-webkit
- Other various minor bugfixes
chokidar repo fix - v1.0.4
- The chokidar dependency moved repos, and though the git URL should have been forwarded some people were having issues. This fixed the repo and version. (v1.0.3 is skipped because it was published with a bad URL, quickly fixed with another version bump)
Bug fixes - v1.0.2
- Use chokidar for watching file changes. This should fix a lot of problems on OS X machines.
- Always use
/
in paths when precompiling templates - Fix bug where async filters hang indefinitely inside
if
statements - Extensions now can override autoescaping with an
autoescape
property - Other various minor bugfixes
We've reached 1.0! Better APIs, asynchronous control, and more
- An asynchronous API is now available, and async filters, extensions, and
loaders is supported. The async API is optional and if you don't do
anything async (the default), nothing changes for you. You can read
more about this
here. (fixes #41) - Much simpler higher-level API for initiating/configuring nunjucks is
available. Read more
here. - An official grunt plugin is available for precompiling templates: grunt-nunjucks
- The browser files have been renamed. nunjucks.js is now the full
library with compiler, and nunjucks-slim.js is the small version
that only works with precompiled templates - urlencode filter has been added
- The express integration has been refactored and isn't a kludge
anymore. Should avoid some bugs and be more future-proof; - The order in which variables are lookup up in the context and frame
lookup has been reversed. It will now look in the frame first, and
then the context. This means that if afor
loop introduces a new
var, like{% for name in names %}
, and if you havename
in the
context as well, it will properly referencename
from the for loop
inside the loop. (fixes #122 and #119)