dust_compiler

A simple Node command line tool that watches and compiles dust templates recursively from one directory to another

Installation

npm install dust_compiler -g

Usage

$ dust_compiler {input path defaults to ./template} {output_path defaults to ./compiles_temlates}

dust_compiler's People

Contributors

Stargazers

Watchers

dust_compiler's Issues

Automatically handle directories as source/target parameters

Currently if a user attempts to point to a particular folder as the source/target parameters but fails to include the trailing slash, dust_compiler will not actually read the last path component as a directory.

It should check whether the last path component actually points to a directory, and if so, handle it as if the user had entered it with a trailing slash.

Handle Template Errors Without Quitting

Currently, if the user saves a template file with an error such that it cannot be compiled, dust_compiler will output the error and then quit. This means the user would have to fix the error and then re-start dust_compiler.

Instead, dust_compiler should log that there is an error, but instead of quitting, it should just skip that file. Once the file is re-saved with the error fixed, dust_compiler will then automatically re-compile the file.

Exclude Non-Template Files

Dust_compiler should not try to compile files that are not actual templates. Unfortunately, it's not just a matter of keeping a separate folder for only template files as currently it will try to compile things like svn metadata files.

The easiest and most obvious solution would be to only try to compile files with certain extensions, such as .html or .dust.

Recommend Projects