While handlebars is able to use the registerHelpers method via a helpersPath option on your
server (or pack) object according to the views property, the jade engine has no compatible mechanisms.

So.. How would you be able to add such functionality in a hapi based application without circumventing the view-initialization completely?

What I wanted to achieve, was a concept like in connect-assets.
Simply put: An asset-pipeline, which is configurable in the view-without much overhead. But to be able to do so, there had to be a helper
in the view which would parse the asset files and transformipileTM them. This would also involve interchanging the
source path in the generated html output for each view.

So you created this nice and shiny new hippster round-edges site for your client and allways press your thumbs
on deployment to make it magically work on the production system. But what if we deploy to a different Webserver
software?

Now you might rapidly approach troubles and pain as you never had before, winding your brain about why the crap your
CSS3 Polyfill accomplished with CSS3PIE doesn’t work as expected (and tested on
your dev-site). This can cause a serious case of grey hair!