Memory leaks suck and they proliferate when you slice & dice the DOM using JavaScript. Edge DevTools makes it easy to debug “detached elements” now.
\n","social_text":"Memory leaks suck and they proliferate when you slice & dice the DOM using JavaScript. @MSEdgeDev now makes it easy to debug “detached elements” in DevTools.","url":"https://www.aaron-gustafson.com/notebook/links/debug-memory-leaks-with-the-microsoft-edge-detached-elements-tool/","external_url":"https://blogs.windows.com/msedgedev/2021/12/09/debug-memory-leaks-detached-elements-tool-devtools/","tags":["JavaScript","DevTools"],"image":"https://blogs.windows.com/wp-content/uploads/prod/sites/33/2021/09/1fcfaeac10ed41b08decb59e35dad86b.png","date_published":"2021-12-09T17:44:40Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/using-the-chrome-devtools-new-code-coverage-feature-ca96c3dddcaf/","title":"🔗 Using the Chrome DevTools new code coverage feature","content_html":"While the name is a bit confusing, this new tool helps you compare the volume of code you’ve authored to the the amount of code that is actually executed by the browser. It’s a cool idea, but you should take it’s results with a grain of salt: This tool is only diagnosing your project based on the current page and/or flow (if it’s a single page app). Be careful not to take the results as gospel and start eliminating code without knowing whether it’s actually unused in all scenarios.
\nNow… tie this into an automated testing tool and gather results from a complete run-through of an app or site and you’ve got something you can actually use to improve your site’s performance.
\nIt’s worth noting that there are static analysis tools for many task runners that can actually run queries against your HTML templates and remove unused styles automatically. I’ve used gulp-uncss on a few projects and found it to work reasonably well (though you have to tune it for any JavaScript-related styles since it only consults your HTML to find matches).