I followed the example.build.js found in the demo directory, but setting all of the pragmas still leaves me with the full Handlebars compiler built into my source.
Grepping 1.0.0 for excludeHbsParser gives no results other than the build config, so I don't think it's actually being used anywhere.
That's the (I think) objective thing I found, now if I may make a couple suggestions:
- The readme could be amended to provide something like the build config to show people how to optimize their build. I suspect most users have the entire Handlebars compiler built into their project
- Could we just adopt the same config as the requirejs text plugin, and use
stubModules for the optimized plugin? To do that you'd need to (a) not require hbs in compiled templates and (b) get it to load handlebars.runtime.js which the compiled templates need, maybe by having users adjust their paths.config
I followed the
example.build.jsfound in the demo directory, but setting all of the pragmas still leaves me with the full Handlebars compiler built into my source.Grepping 1.0.0 for
excludeHbsParsergives no results other than the build config, so I don't think it's actually being used anywhere.That's the (I think) objective thing I found, now if I may make a couple suggestions:
stubModulesfor the optimized plugin? To do that you'd need to (a) not requirehbsin compiled templates and (b) get it to loadhandlebars.runtime.jswhich the compiled templates need, maybe by having users adjust theirpaths.config