4 ms·
If you're using console.log to do debugging then it's worthwhile giving yourself a little more data to point at where a problem might lie - timings. Open up de
by onion2k 6y ago
If you're using console.log to do debugging then it's worthwhile giving yourself a little more data to point at where a problem might lie - timings.
Open up devtools (cmd+option+j), then open the command palette (cmd+shift+P), and then search for "console", and then select "Console - Show Timestamps". Now every console output will have the high definition timestamp prepended to it. That can be really helpful if you don't want to go down the whole perf chart rabbit hole, or if you think things might be running in the wrong order due to some async weirdness.
(This probably only works in Chrome)
- sfink 6y agoIn Firefox, you click on the gear icon in the top right of the console, then check "Show Timestamps". Though you probably want the per-tab Console there (ctrl-shift-k). ctrl-shift-j would give you the multiprocess browser console, which is very noisy.