I'm not thrilled about adding yet another option to this task, but if we do, maybe rename the option to something like handlebarsVariable and force the user to provide the full path? e.g. MyApp.Handlebars. That way if some weird person wants to run Handlebars under a totally different name they can do that too.

I'm not thrilled about adding yet another option to this task

Yeah, same. There were (at least) two issues made about it, though, so I'm sure there are even more people who are looking for the functionality.

maybe rename the option to something like handlebarsVariable and force the user to provide the full path?

Agreed on both counts.

@Kerrick / @trojjer, I'd like to hear your thoughts.

I don't think this is the right way to go about this. Instead of taking handlebarsNamespace and passing the template to handlebarsNamespace.Handlebars.template(), the entire path should be customizable.

For instance, if you wanted templates to be passed to MyNS.doHandlebarsReg(), you should be able to do so. An appropriate name for this would be wrapper.

+1

Edit: Any ETA on this?

@jmeas any thoughts on my comment above?

Honestly, any solution to wrap Handlebars would be better than nothing. In the meantime, for anyone else having the same issues, I've "glued it together" in my own project by using https://github.com/outaTiME/grunt-replace immediately after grunt-contrib-handlebars task:

replace: {
    example: {
        options: {
            usePrefix: false,
            patterns: [{
                match: /Handlebars\./g,
                replacement: 'MyApp.Handlebars.'
            }]
        },
        files: [
            {
                expand: true,
                flatten: true,
                src: 'build/templates.js',
                dest: 'build/'
            }
        ]
    }
}

...which feels like a crime doing this, but it works. Until this issue is fixed anyway.

Closing for lack of activity.