Issue with Async Helpers on Heroku about hbs HOT 4 CLOSED

This needs much more information and example code that can actually be run.

from hbs.

Again, appreciate that it's not a great ticket, just trying to get some insight into what could cause it. Is there a timeout after which the IDs don't get replaced if the promises don't return?

I can create a sample, just worried it won't show the problem since the only current thing that triggers it is Heroku's env vs mine.

from hbs.

Got it, sorry again for being vague. Just in case anyone runs across this with a similar answer, the issue is Express has view caching enabled by default (just in production env). Rough they don't work together, I'll probably investigate more at some point, but if you need to fix, just use:

app.set('view cache', false);

from hbs.

This is still an issue. When NODE_ENV is set to production, express automatically sets view cache to true. Async helpers set an ID that gets replaced by the resolved value, however this only happens on the non-cached version of the template. As soon as the template gets cached, the IDs no longer get replaced. See my pull request #124 for a fix that replaces the async IDs for both cached and non-cached templates.

from hbs.