Totty

> You can compile it with target "node" and run the compiled code. Ok, I will try but for dev is not optimal, right? I remember the last time it...

I've tried both and work pretty good. - With enhanced-require you need more boilerplate code; - With --target node you put the server code in some other folder which might...

I've noticed this and other issues. I would suggest to look into webpack + gulp to improve your code structure. Also another tip would be to use standard names for...

I use a wrapper on your omxdirector lib and in this I do like this when play is called: - if playing omx.stop(cb); // the cb is run when omx...

Hy! Ok, I will try to make it work :-) On Fri, Feb 6, 2015, 22:13 Alessandro Pezzato [email protected] wrote: > I guess this is caused by a workaround. Sometimes...

Thanks On Wed, Feb 4, 2015, 08:16 Alessandro Pezzato [email protected] wrote: > You're right, I'll fix this asap > > — > Reply to this email directly or view it...

Quick fix: I've added the originalRequire to the enhancedRequire and loaded the webdriver-sync with the original node.js require.

By using fibers your code can look like this ``` var a = makeAsyncRequest().wait(); var b = usingAVarInAnotherAsyncRequest(a).wait(); expect(b).to.be(4); ``` While with the current way of doing things is kind...

You are welcome, I've just moved all my server side services to fibers and 100 lines of code with async just transformed in 10 readable lines. Is like magic. No...

Here it is cucumber + fibers + more goodies: https://github.com/hackhat/cucumberry