Explore >> Select a destination
|
You are here 
|
nolanlawson.com | ||
| | | | |
slack.engineering
|
|
| | | | | You might have used Chrome's Developer Tools to profile your JavaScript to improve performance or find bottlenecks. DevTools is fantastic, but there's a lot of potentially useful information that the performance panel doesn't capture. Enter Chrome Tracing: a tool that's built into Chrome (and Electron) that can collect a huge variety of detailed performance data.... | |
| | | | |
arveknudsen.com
|
|
| | | | | Chromium/Google Chrome is my hands-down favourite browser for developing Web sites in, owing toits incredibly sleek developer tools. I feel right at home in its JavaScript console, for evaluating JavaScript interactively or to inspect logs from arunning JavaScript application. However, the latter scenario is somewhat let down by the console's limited search functionality. At the time of writing, the console only lets you search for plain text on a line-by-line basis. If I want to search for regular expressions, which I tend todo, maybe spanning multiple lines, I'll have to paste the console contents into a text editor (Sublime, anyone?) and search in there. | |
| | | | |
blog.chromium.org
|
|
| | | | | Developers of Chrome Apps and extensions have long been familiar with the developer-mode setting of the chrome://extensions tab in the Chr... | |
| | | | |
screenspan.net
|
|
| | | Run single-point-of-failure (SPOF) tests using Puppeteer to see what happens to web page rendering and interactivity when third-party stylesheets and scripts are laggy | ||
