You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Callbacks are tricky though, because we would need some more context from user to correctly understand when user wants to start/stop the timer.
For example, you may profile the code with callbacks with console.time:
We could introduce a similar construct to start/stop the timer (and display the execution time inline). For example: //?.s to start the timer, and //?.e to stop it and print the time. Would something like this work for you?
This should be possible as seen in other tools of this nature.
Could you please share what tools are you referring to?
Absolutely! That's a compromise I'm willing to work with. I believe your other product Wallaby combined with Mocha will give you runtime testing/profiling for code. I abuse a Mocha test in this way to provide that information.
Issue description or question
As the title implies, I would like to profile async/callback code. This should be possible as seen in other tools of this nature.
Sample code
Example output
Quokka.js Console Output
Code editor version
Visual Studio Code
v1.30.1
OS name and version
OSX Mojave
v10.14
The text was updated successfully, but these errors were encountered: