prescore
v0.1.1
Published
Precompile underscore templates into joined amd files
Downloads
8
Maintainers
Readme
PreScore
Compile underscore templates into an amd file.
For now there's only one mode of operation: look for all .html
file under the input paths, and write a single .js
file. The last positional argument is assumed to be the output file; the path is assumed to exist.
By default, a file is generated with a single, anonymous amd define()
, which returns an object mapping template names to the respective functions. See --separate
for an alternative mode of operation.
Options:
--prefix
: use this prefix for the template names (and module names, if using --separate
). E.g. if your input path is foo/bar/templates
and you have a file entry.html
, by default that will define a module define('entry', function()…)
, which is probably not what you want. You can pass a prefix argument --prefix=templates/
, which then gets define('templates/entry', function()…)
.
--require
: require the named module. It will be stored in a variable of the same name, with any non-alphanumeric characters replaced by __
. You can use those in your template (via closure), or in conjunction with --store
. Can be specified multiple times.
--separate
: generate a bundle file with each template as its own amd define()
. With a recent enough RequireJS, you can use this file as a bundle; or you can concatenate it with all your other define()s
for optimized loading.
--store
: in addition to returning the template function from each module definition, also store them in the namespace provided in this argument. The top-level global needs to preexist; any additional sub-objects will be created if undefined. We use this in Backbone views to detect whether or not a template was precompiled, by builing with --store=_.template.precompiled
, so the view can then do this.template = _.template.precompiled[this.$el.selector.substr(3)] || _.template($(this.$el.selector + '_template').html());
. It's not pretty, but it's a viable migration strategy.
This script does no optimization or minification. You'll probably want to join it with other scripts in your app anyway, so we figured that would be redundant.