Are you debugging your JavaScript by writing console.log statements \u2013 the front-end equivalent of using \u201cecho\u201d or \u201cvar_dump\u201d in PHP?<\/p>\n
Being primarily a back-end developer, I was accustomed to using XDEBUG as part of my workflow, but often fell back on rudimentary debugging skills when it came to debugging JavaScript or diagnosing performance issues from the front-end.<\/p>\n
Enter Chrome Developer Tools. It seems that every time I look, this little window in Chrome gets more and more features that save me time and headaches debugging, testing and optimizing my web pages. Whether I\u2019m stepping through JavaScript, Debugging CSS, Testing REST API calls, or auditing page performance, Chrome\u2019s Developer Tools are there to help. In this session, I\u2019ll share with you some of the features that have made this tool an essential part of my toolbox. I\u2019ll show you how how to diagnose a page\u2019s performance issues, audit a page for accessibility, review page security,inspect calls made to the REST API, and more.<\/p>\n","protected":false},"excerpt":{"rendered":"
Are you debugging your JavaScript by writing console.log statements \u2013 the front-end equivalent of using \u201cecho\u201d or \u201cvar_dump\u201d in PHP? Being primarily a back-end developer, I was accustomed to using XDEBUG as part of my workflow, but often fell back on rudimentary debugging skills when it came to debugging JavaScript or diagnosing performance issues from … <\/p>\n