When calls from Jade out to external functions written by ourselves or 3rd parties crash, they take out the node.
Matters are worse still if the logic is running server-side as that will crash the whole environment (jadrap).
The Developer Security Library is an example of a call that runs as a serverExecution and this has previously taken out our main live environment.
Is there any way the Jade product can be improved to be more resilient when calling out to libraries?
Perhaps arm an exception handler to help minimise the fallout?
Any solution would ideally be made in-process, or at least we would need to preserve the current ability to call back into the current Jade process.
This idea is complimentary to the DSL hooks idea previously posted.