Recursively compiles a directory of dust.js templates into grouped .js files.
Dust templates in the root directory are compiled into a templates.js file.
Templates in sub directories of the root are compiled into a file matching the full
directory name (with dots replacing path separator). So all templates at sub/dir/*.dust
would be compiled into sub.dir.js file.
For use in other node projects:
npm install dusting
As a command line tool:
npm install dusting -g
designed to be used synchronously:
var dusting = require('dusting');
dusting({
source: <input>,
output: <output>,
// optionally rename the root `templates.js` file
rootOutput: 'foo.js'
});
command line:
dusting <input> [output]
<source> path to a directory containing dust.js templates (*.dust).[output] directory to write output to, defaults to cwdFAQs
cli and node module to compile dust.js templates
The npm package dusting receives a total of 0 weekly downloads. As such, dusting popularity was classified as not popular.
We found that dusting demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.