Artem Govorov

Hey @samhatoum, can't share any plans about the feature support yet. The team is busy at the moment rushing towards releasing [this big feature](https://github.com/wallabyjs/public/issues/144#issuecomment-227925494). After releasing that one and clearing...

@tedvanderveen The status hasn't really changed, but I'll post an update here when it does.

@jfstephe > ETA on this feature? 1 week? 3 months? 6 months? 12 months? Never? Can you give us a ball-park idea? Unfortunately I can't share ETA at the moment....

@newtack What testing framework are you using with Deno?

@newtack Thanks! What testing framework have you been using in node.js prior to switching to deno? Is the built-in deno test working well for you in terms of performance and...

It's not possible at the moment. We'll investigate the best way to add the feature.

At the moment, wallaby can only run on a dev machine (it has to have a full control over the created node process(es)).

> The docs say the debugger has edit-and-continue, so in theory I could enter the expression right in the code and then select it to see the result, but in...

Some update: we have identified a couple of issues that may have been causing Wallaby debugger edit-and-continue stop working after syntactic errors introduced while typing an expression to evaluate (in...

Thanks for providing the sample, we'll investigate it. > Would it be safe to assume the rest of the context (i.e. the stack) was preserved, and I can just step...