It looks like scope variables can't be accessed given the existing implementation of include, is that right?

I think it means that iteration like the following is impossible within a 'parent' template, since it's only the options which are made available to the subtemplate, and it's currently impossible to modify the options themselves.

        _.forIn(questions, function(question, questionIdx){
            var answer = answers[questionIdx]
            print(include("editor_form_field"));
        })

Thanks for underscore-express.

It's a real inspiration and is already fixing some serious architectural issues for me, by being able to wrangle my own 'DSL' for my app's very specific templating needs.

However, there's a missing callback argument in the embedded call to render made by the include(...) function. Because there's no cb passed in, the sync error handling clause is hit and the node server gets taken down by errors in sub-templates.

To fix it, you just change the line...

var str = render(path.resolve(dir, rel + '.' + ext), options);

...to read...

var str = render(path.resolve(dir, rel + '.' + ext), options, cb);

...and then the error handling gets passed down the middleware path to the proper location.