Manuel Ernst

thanks @busser that helped.

sure, no problem: ``` var dust = require('dustjs-helpers'); ``` when requiring, the lib checks for a global available dust instance, if not available, it requires dust and exports it. (https://github.com/linkedin/dustjs-helpers/blob/master/lib/dust-helpers.js#L514)...

exactly. a sane way without clobbering the global namespace would be something like this: ``` var dust = require('dustjs-linkedin'); require('dustjs-filters-secure').enhance(dust); require('dustjs-helpers').enhance(dust); ```

I'm curious regarding the use-case of setting a field dirty when it is focused, maybe you can elaborate real quick @eden-omb ?

@rvion I'm currently seeing a similar issue, the error "Connection terminated unexpectedly" has come up, afterwards the connection was not queryable anymore ("Client has encountered a connection error and is...

actually i tried `setTimeout` simply to test a delayed response from a worker thread. i do not have an actual usecase.

looks like it's related to #16

NaN (https://github.com/nodejs/nan) abstracts such native incompatabilities that are introduced with every new v8 version