-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node.js and npm support #53
Comments
Also curious about this? I end up having to make a whole bunch of tweaks to get handlebars running in node (changing require to be relative, etc). Would be nice if it worked properly out of the box, but I'm unclear if it's intentional for some other usage, or if it's just a bug? |
It would be nice if handlebar was an npm package that we can easily use with node.js |
Would be awesome if you could pre-compile your templates with node and push them out as functions available in some handlebars template object. I know the Jammit-asset-packager does something like this with underscore templates. |
Yeah .. please make this to a npm module so we can use it on node.js. It's gonna make it more popular and more are going to contribute :) |
+1 |
I submitted a pull request for this: #90, please let me know if something seems wrong/out of place! |
Cool .. merge it! |
Please do add this |
I'm marking this a duplicate of #90. |
Any idea of when #90 will be pulled? Others have recommended I publish this to NPM on my own, but I'm wary of doing that, especially if you guys will take ownership over it in short order... |
There's actually an NPM package up now that someone else posted. We'll get an official package up by the time we release 1.0. |
Looking forward to 1.0 and a package for node. ;) |
Did this ever get completed, is Handlesbars easily support under node.js? |
How is
handlebars.js
expected to be used in node.js?I see that object
handlebars
is being exported asexports.parser
but the full Handlebars functionality as documented is only implemented only byHandlebars
object.Is there a reason why it's this way? Also, Is there a reason why handlebars.js is not a
npm
package?The text was updated successfully, but these errors were encountered: