broken template precompilation

[AAS]

./handlebars template.html

produces always same output:

(function() {
  var template = Handlebars.template, templates = Handlebars.templates = Handlebars.templates || {};
})();

Tested with node v0.10.24 on Windows7 x64, handlebars 1.2.1

[kpdecker]

Does this resolve the issue?

./handlebars --extension=html template.html

[AAS]

Yes, now it produce proper code. Thank you.
But with this approach Handlebars.templates contains 'template' function instead of 'template.html'

[kpdecker]

We need to allow explicit files to be passed, ignoring the extension filter.

[andres-torres-marroquin]

What's the reason behind --extension? Handlebars shouldn't be able to render any kind of file/type/language? I just can't wrap it on my mind.

[kpdecker]

Extension is intended to be used for recursive file handling so you don't include content that is not a handlebars template. Say you had javascript source files living next to the handlebars templates, for example.

It's operating incorrectly here in that it's filtering files that are explicitly passed.

[cstockton]

Just ran into this, some build scripts that were compiling templates just fine no longer work. I pass a list of full file names, with extensions of ".hbs". There is NO output or anything to indicate to me what is going on. I spent a good amount of time troubleshooting before I came across this bug thanks to google. Moving forward I have a couple of suggestions.

First; if FULL file paths are still being ignored (the latests npm install I did appears to be the case) I think it should be fixed- to not require a extension argument when the file path is full.

Second; if NO files were found due to ignoring due to extensions argument, some STDERR with a hint would be nice, or perhaps a /* comment */ in the stub saying "Did you forget to include a extensions argument?" if it's missing.

[kpdecker]

Released in v2.0.0-alpha.1