/explore
|
You are here 
|
ading.dev | ||
| | | | |
arveknudsen.com
Adding Support for Regular Expression Search in the Chromium Developer Console | Arve Knudsen's Blog 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. |
|
| | | | | ||
| | | | |
piware.de
[AI summary] The blog post discusses the migration from PhantomJS to the Chrome DevTools Protocol for testing Cockpit's web interface, highlighting the reasons for the switch, evaluation of alternatives, and challenges faced during the transition. |
|
| | | | | ||
| | | | |
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.... |
|
| | | | | ||
| | | | |
www.aleksandrhovhannisyan.com
Comment systems can be a pain to set up, but they don't have to be. Learn how to use the GitHub Issues API to create a custom comment system powered by Netlify functions. |
|
| | | |||
