Will replace the {{{body}}} tag with the contents of index.hbs.
Now, on the client side I'm using Backbone.js and want to use Handlebars for the views controlled via Backbone. The problem is that because these pages are already rendered through Handlebars, when I attempt to use Handlebars within it (or Handlebars within Handlebars) it doesn't work. There are no errors, it simply just doesn't replace tags with data.
Has anyone encountered this before or have any idea a work around?
Thank you!
回答1:
Yup, it's a sticky problem --- kind of like the quoting problems in shell scripts which become a rats' nest of quoted quotes.
My solution is to use jade (a la haml) in expressjs (server-side) to output handlebars based templates for the client. This way, the server uses one syntax (jade), and the client uses another (handlebars). I am at the same crossroads as you, so I have the same challenge.
Of course, jade is not essential (though it's ready-made for expressjs). You could choose any (non-handlebars) template engine for the server, and/or you could use handlebars on the server with your non-handlebars templating on the client --- as long as the two syntaxes of your chosen templating engines do not collide. Since I'm using emberjs on the client and it uses handlebars syntax (by default), I prefer using emberjs + handlebars syntax on the client. So expressjs + jade became a natural fit for the server.
回答2:
You should use pre-compiled client templates. They are faster executing and allow you to use the same template language on the server and client.
I whipped it up in a couple hours based on the command-line compiler in wycats' handlebars repo. It's not the greatest code in the world, but it's been getting the job done for me very well.
EDIT: I am no longer maintaining this package. If you would like to take over, please contact me via Github. I mainly use Jade templates now, so it doesn't make sense for me to continue as the maintainer.
回答5:
I have worked around this by passing client-side templates through server-side templates.
So on the server-side read all your client-side templates to an array and pass it to your render function on the server-side
Here I'm using file names without extensions as the template id so that they can be referenced from Backbone views. Oh, and remember to implement caching for production mode.
Yeah, this sucks.
I think we should write a Handlebars/Express/Connect helper for this.
回答6:
You have 2 options. The second is THE best way to go:
1) Escape the mustaches
2) Precompile
This will compile the template on the server before it goes to the client. This will make the template ready to use and reduces the burden on the browser.
回答7:
I didn't like the precompilation solution (because I want to define templates in the same file where I will use them) nor the naive \{{ escape solution (because it needs the full Handlebars compiler and more javascript code) so I came up with an hybrid solution that uses Handlebars' helpers:
1) Register a new helper called "template" on server configuration
var hbs = require('hbs'); hbs.registerHelper("template", function(key, options){ var source = options.fn().replace("\\{{", "{{"); var ret = ''; return ret; });
2) Use it anywhere in your client-side webpage (with \{{ escape for client-side parameters)
{{#template "myTemplate"}}
Hello \{{this.name}}!
{{/template}}
(the server will precompile it in something like this)
3) Simply call the function where you need it in client-side javascript