An interesting bug arises when both engine and imports are used: imports are correctly loaded from the specified engine and passed to the template function, but the _ symbol inside of the template function refers to the global _ instead of the engine's one.
An interesting bug arises when both engine and imports are used: imports are correctly loaded from the specified engine and passed to the template function, but the
_
symbol inside of the template function refers to the global_
instead of the engine's one.I pinned down the problem to the usage of the
Function()
syntax, here's a CodePen to prove my point: http://codepen.io/anon/pen/JRybKm?editors=0012I think it can be easily solved by passing the engine directly in the call to Function alongside the other imports, I will file a PR to fix it soon.