Consider publishing handlebars-runtime as a separate module on npm

[dlmanning]

This would enable those of us who've written things like browserify transforms for handlebars to not do things like this:

https://github.com/dlmanning/browserify-handlebars/blob/master/index.js#L8-L9

and this:

https://github.com/epeli/node-hbsfy/blob/master/runtime.js#L1-L3

which can only lead to tears.

I've commented on an open issue in https://github.com/epeli/handlebars-runtime, whose author currently holds the name on npm:

esamattis/node-handlebars-runtime#3

/cc @epeli

[kpdecker]

Example from the discussion re: allowing the runtime to be accessed from the canonical module:
https://github.com/epeli/node-hbsfy/blob/master/runtime.js

[dlmanning]

That's just as subject to future-breakage, as it still depends on the internal path to the runtime. E.g. that example is broken with the latest version of handlebars, since you've started using the transpiler.

[esamattis]

I think the best option would be to have a documented runtime.js inside the handlebars package itself which then could be required like this:

var Handlebars = require("handlebars/runtime");

for runtime usage only.

[dlmanning]

That's a terrific idea. 👍

[kpdecker]

Yep, this is the plan.

On Mon, Dec 9, 2013 at 1:39 PM, David Manning notifications@github.comwrote:

that would be good

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/668#issuecomment-30165805
.

[kpdecker]

Released in 1.2.0