easytemplate is a simple system for initializing new projects. It only requires a project skeleton and a short configuration file.
Deno must be installed to run easytemplate.
git clone https://github.com/Jamalam360/easytemplate
cd easytemplate/example
deno run --allow-read --allow-write https://raw.githubusercontent.com/Jamalam360/easytemplate/main/easytemplate.ts
A more complex example can be found here
easytemplate can also be run with the --debug flag to debug your templates (or
more likely easytemplate itself).
An easytemplate template is simply composed of the relevant files along with an
easytemplate.json file, which is removed at the end of
templating.
The configuration file is composed of the following fields:
{
"inputs": "Input[]",
"move": "Move[]",
"exclude": "string[]"
}Inputs are the questions which are asked to the user before filling in the template. All inputs share 4 common fields:
id: string; this is the name of the variable that will be passed to Handlebars.label: string; this is the prompt shown to the user.default?: T; this is the default response.only_if?: string; this is a JavaScript expression which determines whether the user should be prompted about this input. All previously evaluated inputs are available (e.g.some_previous_input.includes("jeff")).
{
"type": "options",
"id": "some_id",
"label": "Enter ...:",
"options": [
{
"value": "john",
"label": "John"
},
{
"value": "bill",
"label": "Bill"
}
]
}{
"type": "string",
"id": "some_id",
"label": "Enter ...:",
"regex": "optionally add a validating regex"
}{
"type": "boolean",
"id": "some_id",
"label": "Enter ...:"
}Move operations are used to rename/move files after the template has been filled out (all Handlebars expressions have been expanded).
{
"from": "from_path",
"to": "to_path"
}Excludes are used to exclude some files from being templated. Exclude paths are extended, globstar-enabled globs.
easytemplate makes a best guess at automatically excluding non-text files from processing.
Ignore paths are used to exclude files from the final initialized template. Ignore paths are extended, globstar-enabled globs.
easytemplate uses Handlebars as it's templating engine. Handlebars is useable in any file, as well as in directory paths/file names themselves.
Since file paths cannot contain /, which is used by Handlebars, easytemplate
will replace all occurrences of %% in a path with /. Other than this,
Handlebars can be used as normal in path names - here is a complex example,
along with an example output:
./my_template/{{ variable1 }}/{{ #replace "b" "a" }}{{ variable2 }}{{ %%replace }}/{{ variable3}}.txt
###
variable1 = james
variable2 = bob
variable3 = dave
./my_template/james/aoa/dave.txt
easytemplate includes a few default Handlebars helpers.
Replaces all occurrences of find in the block with replace
{{ #replace 'find' 'replace' }}
I am finding this string, very cool!
{{ /replace }}
###
I am replacing this string, very cool!
Implements the following binary operators between variables:
=====!=!==<<=>>=&&||
{{ #ifCond string1 '===' string2 }}
string one was equal to string two!
{{ /ifCond }}
###
string1 = test
string2 = test
string one was equal to string two!
When using easytemplate myself, I found some IDEs that I had configured to format code automatically would create horrible formatting due to the random Handlebars syntax in what the IDE thought was a normal code file.
Due to this issue, I made easytemplate remove the .easytemplate suffix from
any files that have it. Other than that, no other changes are made to these
files outside of the usual processing.
Options:
--debug: enable debug logging; mainly just helpful for me--disable-interactive-mode: don't prompt for inputs, useful for CI environments. Must use along with--input.--input: pass a value for a input, in the formid=value, e.g.--input my_string="a string here". Quotes are optional.