<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bivi shan on Medium]]></title>
        <description><![CDATA[Stories by Bivi shan on Medium]]></description>
        <link>https://medium.com/@bivishan8686?source=rss-8f8e54fbcdfd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YYkQUgLHIPbIYAGfrvsq3A.jpeg</url>
            <title>Stories by Bivi shan on Medium</title>
            <link>https://medium.com/@bivishan8686?source=rss-8f8e54fbcdfd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:04:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bivishan8686/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Mastering Server Debugging in VS Code: A Simple Guide Using Built-in Tools [ Part-1]]]></title>
            <link>https://medium.com/@bivishan8686/mastering-server-debugging-in-vs-code-a-simple-guide-using-built-in-tools-part-1-dae12341a54f?source=rss-8f8e54fbcdfd------2</link>
            <guid isPermaLink="false">https://medium.com/p/dae12341a54f</guid>
            <dc:creator><![CDATA[Bivi shan]]></dc:creator>
            <pubDate>Tue, 06 May 2025 10:23:34 GMT</pubDate>
            <atom:updated>2025-05-06T10:23:34.389Z</atom:updated>
            <content:encoded><![CDATA[<p>Debugging is an essential skill in a developer’s toolkit. If you’re using <strong>Visual Studio Code (VS Code)</strong>, you’re in luck — it comes packed with a powerful, built-in debugger that can save hours of frustration.</p><p>In this post, I’ll walk you through how to use the built-in debugging tools for server environment in VS Code, step-by-step, in the simplest way possible. Whether you’re a beginner or someone who’s switching from another editor, this guide is for you.</p><h3>🧰 Why Use the Built-in Debugger in VS Code?</h3><p>Before we dive in, let’s understand <em>why</em> you’d want to use this debugger:</p><ul><li>No need for external tools or configurations.</li><li>Integrated UI with breakpoints, variable inspection, call stack, and more.</li><li>Seamless experience with multiple languages and extensions.</li><li>Works right out of the box with most projects.</li></ul><h3>🚀 Getting Started with Debugging in VS Code</h3><h4>1. Open Your Project in VS Code 🌌</h4><p>Make sure you’ve opened your project folder — not just a single file. VS Code needs access to your full project context.</p><h4>2. Set a Breakpoint 🔴</h4><ul><li>Open any .js, .jsx, .ts, or .tsx file.</li><li>Click to the <strong>left of the line number</strong> where you want execution to pause.</li><li>A <strong>red dot</strong> will appear — that’s your breakpoint (meaning, where you want to stop the code execution and see what’s happening on the right way).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/1*FAJn3tVeO_RY8vfy7if9VA.png" /><figcaption>click on prior to the any line of code where you want to set the breakpoint</figcaption></figure><h4>3. Start the Debugger 🧷</h4><p>Depending on whether you’re debugging the <strong>backend (Node.js)</strong> or the <strong>frontend (React with CRA)</strong>, the process differs slightly.</p><ul><li>For server debugging, at first you have to add one line of code of script inside yourpackages.jsonfile inside your server directory, which is</li></ul><blockquote>“start: node server.js”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*W0wGlJXfs85H8xCgrW6ORQ.png" /><figcaption>one line of code in red underline</figcaption></figure><ul><li>Then, switch to server directory by cd server in your terminal.</li><li>Then, press ctrl+shift+D in windows. [<em>in mac, i know i don’t have to instruct you 😋</em>]</li><li>Go to the <strong>Run and Debug</strong> panel</li><li>Click <strong>“create a launch.json” (</strong>just slight underneath the Run &amp; Debug panel), then choose <strong>Node.js</strong>.</li><li>Now, simply choose Run script:start</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*k17XlRCAJpd6fodg-NKNxg.png" /><figcaption>this option appears only after configuration in packages.json</figcaption></figure><ul><li>Now, choose option Run Script: Start and click on that play green button to start your debugging.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/361/1*MGwskOPy5t-A3GyDfBmuxA.png" /></figure><ul><li>Now, you will encounter with the various debugging options.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*5jAD9Y5r8OdDicoejXb4FA.png" /><figcaption>all the button will active when you hit the request</figcaption></figure><h3>🧭 Key Features to Use</h3><ul><li><strong>Breakpoints:</strong> Pause execution at specific lines.</li><li><strong>Step Over / Step Into / Step Out:</strong> Control the flow of code execution line by line.</li><li><strong>Watch:</strong> Monitor specific variables or expressions.</li><li><strong>Call Stack:</strong> View the path of function calls leading to the current line.</li><li><strong>Variables:</strong> Inspect current values in real time.</li></ul><h3>🧠 Tips to Make Debugging More Efficient</h3><ul><li>Name your breakpoints for quick identification.</li><li>Use conditional breakpoints to pause only when a specific condition is true.</li><li>Leverage the console inside the debug panel for quick checks.</li><li>Group variables and expressions in the <strong>Watch</strong> section.</li></ul><h3>🔚 Final Thoughts</h3><p>VS Code’s built-in debugger is a hidden gem. It’s intuitive, flexible, and powerful — and once you start using it, there’s no turning back.</p><p>Whether you’re debugging JavaScript, Python, or any other supported language, taking full advantage of these built-in tools can dramatically improve your development workflow.</p><h3>💬 What’s Next?</h3><p>I’ll be sharing more hands-on debugging tips and language-specific configurations in future posts. Let me know in the comments: <em>What’s your biggest pain point while debugging?</em></p><p>📌 <strong>Follow me for more practical dev tips, especially around VS Code and productivity. </strong><a href="https://www.linkedin.com/in/bivishan-sapkota-68a515135/"><strong>LinkedIn</strong></a><strong> || </strong><a href="https://stackoverflow.com/users/11409943/bivishan-sapkota"><strong>StackOverFlow</strong></a><strong> || </strong><a href="https://www.facebook.com/bivishan.sapkota"><strong>Facebook</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dae12341a54f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>