just being curious, I found that consolidate reads the template and handles the string to nunjucks renderString:
|
exports.nunjucks = fromStringRenderer('nunjucks'); |
|
read(path, opts, function(err, str) { |
so may I consider it safe not to specify the loaders when creating a custom nunjucks environment with options.nunjucksEnv, which defaults to using a filesystem/webloader loader with app/views/views as it's root path? in other words, will this behavior change?
also, I didn't see any sign of active maintainence for this repository, is this library deserted?
just being curious, I found that consolidate reads the template and handles the string to nunjucks
renderString:consolidate.js/lib/consolidate.js
Line 1329 in ec2e1ae
consolidate.js/lib/consolidate.js
Line 182 in ec2e1ae
so may I consider it safe not to specify the loaders when creating a custom nunjucks environment with
options.nunjucksEnv, which defaults to using a filesystem/webloader loader withapp/views/viewsas it's root path? in other words, will this behavior change?also, I didn't see any sign of active maintainence for this repository, is this library deserted?