Echo JS 0.11.0

<~>

chinchang 3045 days ago. link 1 point
Just realised a use case where screenlog.js is extremely useful...in JavaScript environments where there is no console! like debugging on a mobile device (ofcourse you can use remote debugging, but this is lot simpler and in the flow)
sbruchmann 3046 days ago. link 1 point
Quote from README.md:

  > Ever faced a situation where you said "Why doesn't this
  > bug show up when developer console is open!!"? And since
  > the bug doesn't show when you have console open, you
  > cannot do debug logging using console.log.

I’m actually interested if anyone had been in this situation.
chinchang 3045 days ago. link 1 point
The reason behind such scenarios is that when the developer console is open, there are a lot of processes that come into play over the code that runs due to stats being collected, debugger being run and what not. All these processes sometimes  affect the reproduction of an issue if the issue is timing based and sometimes auto corrects if the code runs a little slow or late. Hope I am able to explain that a bit.

Besides using in such cases, screenlog.js is extremely useful in JavaScript environments where there is no console! like debugging on a mobile device (ofcourse you can use remote debugging, but this is lot simpler and in the flow)
sbruchmann 3045 days ago. link 1 point
Yeah, I didn’t think of race conditions and stuff like that. Seems reasonable to me. Thank you for clarifying this.