<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Learn DevTools</title><link>https://learndevtools.now.sh/docs/guides/sources/</link><description>Recent content on Learn DevTools</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://learndevtools.now.sh/docs/guides/sources/index.xml" rel="self" type="application/rss+xml"/><item><title>Conditional Breakpoints</title><link>https://learndevtools.now.sh/docs/guides/sources/2-conditional-breakpoints/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://learndevtools.now.sh/docs/guides/sources/2-conditional-breakpoints/</guid><description>These allows to break at a particular line only if a specific condition is evaluated to be true.
The condition can include any variable in code that is available at that particular line. Even the variables inside the closures can be accessed in the condition evaluation.
Try Open Sources tab with file 2-conditional-breakpoint.js Right-click on the line number and add a conditional breakpoint inside dataProcessor() function Add condition index &amp;gt; 3 in debugger window Click on the button to trigger a loop.</description></item><item><title>Content Overrides</title><link>https://learndevtools.now.sh/docs/guides/sources/3-content-overrides/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://learndevtools.now.sh/docs/guides/sources/3-content-overrides/</guid><description>Overrides are a way to test/execute changes without modifying source code. Overridden files are saved in a local folder and served from there for subsequent requests.
In order to use this,
Select a folder on local machine for chrome to save the modified version of files Once chosen, edit any file and hit CMD/Ctrl + S to save the file to overrides folder Once the file is saved, reload the page so that chrome can use the overridden file on page load.</description></item><item><title>Logging Without console.log</title><link>https://learndevtools.now.sh/docs/guides/sources/1-logging-in-browser/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://learndevtools.now.sh/docs/guides/sources/1-logging-in-browser/</guid><description>Chrome provides you an option to add logging statements without the actual console.log statement in your code.
Try Open Sources tab with file 1-logging.js Right-click on the line number to add a logpoint inside randomGenerator() function Add some variable inside the add logpoint window to see the values of those variables being logged. Click on the button below to trigger the function call Start/Restart Processing Preview</description></item><item><title>Request Breakpoints</title><link>https://learndevtools.now.sh/docs/guides/sources/4-request-breakpoints/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://learndevtools.now.sh/docs/guides/sources/4-request-breakpoints/</guid><description>How many times have you wanted to stop before sending an API call or just try to understand where the API call is initiated and the context at the time? This is a very common need when working with sites that have many API requests.
Luckily, the devtools have a way to debug it.
In sources panel, there is a section named XHR/fetch breakpoints Adding URL(s) to this section will pause the execution before a call to those added urls are invoked PS: URLs doesn&amp;rsquo;t need to be of full length.</description></item></channel></rss>