<?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 Menghong Chhay on Medium]]></title>
        <description><![CDATA[Stories by Menghong Chhay on Medium]]></description>
        <link>https://medium.com/@chhaymenghong?source=rss-29f5c3289891------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nZO-RVjlesyqB2pfocMXEw@2x.jpeg</url>
            <title>Stories by Menghong Chhay on Medium</title>
            <link>https://medium.com/@chhaymenghong?source=rss-29f5c3289891------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:14:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chhaymenghong/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[Switch Between Projects Like a Pro: Quick Guide on VS Code’s Project Manager Extension]]></title>
            <link>https://medium.com/@chhaymenghong/switch-between-projects-like-a-pro-quick-guide-on-vs-codes-project-manager-extension-631cf00553d?source=rss-29f5c3289891------2</link>
            <guid isPermaLink="false">https://medium.com/p/631cf00553d</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[vscode-extension]]></category>
            <category><![CDATA[vscode-keyboard-shortcuts]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Menghong Chhay]]></dc:creator>
            <pubDate>Tue, 08 Aug 2023 02:13:51 GMT</pubDate>
            <atom:updated>2023-08-08T02:13:51.800Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey there! If you’re anything like me, you’ve probably got a bunch of different projects going on at once. It’s kind of like having a lot of plates spinning, and you’re running around with sticks, trying to keep them all in the air.</p><p>You know the drill: open up a VS Code window here, another one there, and then dive into the endless maze of folders to find what you’re looking for 😂. Open them up one by one, and before you know it, your desktop is a wild jungle of windows. It’s a hassle, and let’s face it, who has the time for that?</p><p>I mean, wouldn’t it be cool to have all your projects in one neat place, ready to pop open with just a click? No more digging through folders like you’re on a treasure hunt without a map.</p><p>Well, guess what? There’s a way to do just that, and it’s not some secret hack reserved for coding wizards. It’s an extension called <strong>Project Manager</strong> created by <strong>Alessandro Fragnani</strong>, and it’s right there in VS Code, waiting to make your life a whole lot easier. Ready to check it out? Let’s dive in!</p><h3><strong>Quick setup</strong></h3><p>First thing first, we need to get our hands on the “Project Manager” VSCode extension. No worries, it’s not like finding a needle in a haystack. In fact, it’s a piece of cake. Here’s how:</p><ol><li>Fire up Visual Studio Code, and let’s get the party started. 😂</li><li>Head to the Extensions Tab: Look for the square icon on the sidebar, or just hit Ctrl+Shift+X on Windows or Command+Shift+X if you&#39;re on Macs.</li><li>Search for “Project Manager”: Type it into the search bar. You’ll feel like a kid in a candy store with all these extensions, but stay focused!</li><li>Click ‘Install’: Found it? Great! Click on the ‘Install’ button, and let VS Code do its magic.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pAGG2Ig7SdfiAL6gzXz_Kw.png" /><figcaption>Show how to install Project Manager extension</figcaption></figure><h3><strong>What Now?</strong></h3><p>Now that we’ve got the Project Manager extension installed, you might be eagerly opening up the window, expecting to see your projects all lined up. But wait — it’s empty! (nothing) 😂 Don’t worry; that’s just because we haven’t added any projects yet. It’s like moving into a new house; you’ve got to furnish it first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W9aJSvNjS9oIsKYeNm_p3A.png" /><figcaption>Show no project in Project Manager window</figcaption></figure><p>So, how do we start filling up this blank canvas? There are two ways to do this:</p><h4><strong>#1 Manually add new projects to projects.json file:</strong></h4><ul><li>First, open VSCode command palette (command + p) and type as followed and click on “Edit Projects”. This will open up a file called <strong>projects.json</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yOyioLDg4IYtPXpfhtobbg.png" /><figcaption>Search for edit projects in VSCode command palette</figcaption></figure><ul><li>Insert the content below into the file, and customize the values for the “name” and “rootPath” fields to match your specific situation. As for the “tags,” you can add whatever suits you; they’ll serve as a convenient filter or grouping option.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FzRKDcHes7MpElKWhfoVFg.png" /><figcaption>add each project info to projects.json file</figcaption></figure><ul><li>Now, all your beloved projects are gathered in one spot. Clicking on any of them will launch a new VS Code window with that specific project opened. Additionally, you have the option to change the view of the project list, grouping them by the tags you’ve assigned, as follows:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*94nDVnj9qo01xoM4rYSSfw.png" /><figcaption>Show favorite projects grouped by tag</figcaption></figure><h4><strong>#2 Auto add projects that are git version controlled</strong></h4><p>If you’re dealing with a multitude of projects, the idea of adding them individually might not sound appealing. In such a scenario, if all those projects are under Git version control, you can streamline the process by following these steps.</p><ul><li>Click on “Open Settings” as depicted below, and then enter the path to the topmost directory that houses all your projects. Once you’ve done that, simply click “OK.”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Et2EKEYh7a7zijyWmVt-Eg.png" /><figcaption>Show how to automatically add multiple git version controlled projects</figcaption></figure><ul><li>Now all the projects show up as depicted below.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vvJyIftasBEe5FCmHhhl7Q.png" /><figcaption>Show git version controlled projects automatically added</figcaption></figure><p>Thanks for sticking with me through this adventure in project management! I hope you find the “Project Manager” extension for VS Code as handy as a Swiss Army knife. No more diving into the endless abyss of folders. Now, all your projects are right at your fingertips, ready to be tackled with ease.</p><p>Give it a whirl, and let me know how it goes. Here’s to a smoother, more organized coding life. Happy coding, and catch you on the next one! 😂🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=631cf00553d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Deep Dive into VSCode Tasks: Improve Your Developer Workflow Today!]]></title>
            <link>https://medium.com/@chhaymenghong/a-deep-dive-into-vscode-tasks-improve-your-developer-workflow-today-8a75e40e0f0a?source=rss-29f5c3289891------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a75e40e0f0a</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[vscode-extension]]></category>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Menghong Chhay]]></dc:creator>
            <pubDate>Sun, 06 Aug 2023 07:29:12 GMT</pubDate>
            <atom:updated>2023-08-06T07:37:55.727Z</atom:updated>
            <content:encoded><![CDATA[<p>Developers are always on the hunt for tools and techniques that can help streamline their workflows. One such powerful tool integrated within Visual Studio Code (VSCode) is the <strong>tasks</strong> mechanism. In this article, we’ll delve into the concept of VSCode <strong>tasks</strong> and see how they can be incorporated into a developer’s routine.</p><h3>What is VSCode Tasks?</h3><p>VSCode <strong>tasks</strong> are <strong>automation</strong> processes that you can define within VSCode to help you <strong>build</strong>, <strong>test</strong>, <strong>package</strong>, and <strong>deploy</strong> your projects. These tasks can be as simple as running a shell command or as complex as triggering a multi-step build process. The real power of VSCode tasks lies in their ability to link directly with a project’s build system or other tools, such as NPM scripts.</p><h3>Integrating VSCode Tasks into Your Workflow</h3><p>Here’s a step-by-step guide on how you can use VSCode tasks:</p><ol><li>Define Tasks: The heart of the tasks system is the <strong>tasks.json</strong> file. Here, you specify what tasks you want, how they should be executed, and under what conditions.</li><li>Link to External Tools: VSCode tasks can be linked to external tools like NPM. So, if you have a <strong>package.json</strong> with various scripts defined, your <strong>tasks.json</strong> can directly call these scripts.</li><li>Run &amp; Debug: Once defined, tasks can be easily run through VSCode’s Command Palette or can even be bound to a key combination for quicker access. Better yet, you can also download an extension to make running each of these tasks a one click process.</li><li>Group &amp; Organize: Tasks can be grouped, and default tasks can be defined, making the management of multiple tasks easier.</li></ol><h3>A Practical Example</h3><p>Consider the following <strong>package.json</strong> and <strong>tasks.json</strong> files:</p><pre>// sample package.json file<br>{<br>  &quot;name&quot;: &quot;appName&quot;,<br>  &quot;scripts&quot;: {<br><br>    // serve the app locally<br>    &quot;start&quot;: &quot;webpack serve&quot;,<br><br>    // build the app for production<br>    &quot;build&quot;: &quot;webpack --mode=production&quot;,<br><br>    // run unit tests<br>    &quot;unitTest&quot;: &quot;jest&quot;,<br><br>    // run e2e test<br>    &quot;e2e:&quot;: &quot;npx playwright install &amp;&amp; npx playwright test --config=playwright.config.ts --trace on&quot;,<br><br>    // run e2e test using playwright ui mode<br>    &quot;e2e:uiMode&quot;: &quot;yarn e2e --ui&quot;,<br><br>    // run playwright code generation to help with writing e2e tests<br>    &quot;codegen&quot;: &quot;npx playwright codegen appName.com&quot;<br>  }<br>}</pre><pre>// sample tasks.json file. make sure to add it to your .vscode folder in your project<br>{<br> &quot;version&quot;: &quot;2.0.0&quot;,<br> &quot;tasks&quot;: [<br>  // this object represents a single task used to serve the app locally<br>  {<br>   &quot;type&quot;: &quot;npm&quot;,<br>   // this references the &quot;start&quot; script in the sample package.json file above<br>   &quot;script&quot;: &quot;start&quot;,<br>   // this specifies the path of your package.json file which contains the script<br>   &quot;path&quot;: &quot;src&quot;,<br>   // just a simple label for this task<br>   &quot;label&quot;: &quot;Start app locally&quot;,<br>   // additional description for this task. It doesn&#39;t have to be the content of the script<br>   &quot;detail&quot;: &quot;webpack serve&quot;<br>  },<br>  {<br>   // this task is for building the app bundle<br>   &quot;type&quot;: &quot;npm&quot;,<br>   &quot;script&quot;: &quot;build&quot;,<br>   &quot;path&quot;: &quot;src&quot;,<br>   &quot;label&quot;: &quot;Build the app&quot;,<br>   &quot;detail&quot;: &quot;webpack --mode=production&quot;<br>  },<br>  {<br>   // this task is for running the unit test via Jest<br>   &quot;type&quot;: &quot;npm&quot;,<br>   &quot;script&quot;: &quot;test&quot;,<br>   &quot;path&quot;: &quot;src&quot;,<br>   // this attribute is used to group relevant tasks together<br>   &quot;group&quot;: {<br>              &quot;kind&quot;: &quot;test&quot;,<br>              // make this task a default task within this &quot;test&quot; group<br>              &quot;isDefault&quot;: true<br>            },<br>   &quot;label&quot;: &quot;Run unit test&quot;,<br>   &quot;detail&quot;: &quot;Run unit test using jest&quot;<br>  },<br>  {<br>   // this task is for running playwright end to end test<br>   &quot;type&quot;: &quot;npm&quot;,<br>   &quot;script&quot;: &quot;e2e&quot;,<br>   &quot;path&quot;: &quot;src&quot;,<br>   &quot;problemMatcher&quot;: [],<br>   &quot;label&quot;: &quot;Run e2e test&quot;,<br>   &quot;detail&quot;: &quot;npx playwright install &amp;&amp; npx playwright test --config=playwright.config.ts --trace on&quot;,<br>   &quot;group&quot;: {<br>    &quot;kind&quot;: &quot;test&quot;,<br>   },<br>   // use this to inject certain Node JS environment variables to be used by your test<br>   &quot;options&quot;: {<br>    &quot;env&quot;: {<br>     &quot;TESTCLOUD&quot;: &quot;prod&quot;<br>    }<br>   }<br>  },<br>  {<br>   // this task is for running playwright end to end test in ui mode<br>   &quot;type&quot;: &quot;npm&quot;,<br>   &quot;script&quot;: &quot;e2e:uiMode&quot;,<br>   &quot;path&quot;: &quot;src&quot;,<br>   &quot;label&quot;: &quot;Run e2e test in UI mode&quot;,<br>   &quot;detail&quot;: &quot;yarn e2e --ui&quot;,<br>   &quot;group&quot;: {<br>     &quot;kind&quot;: &quot;test&quot;,<br>   },<br>   &quot;options&quot;: {<br>    &quot;env&quot;: {<br>     &quot;TESTCLOUD&quot;: &quot;prod&quot;<br>    }<br>   }<br>  },<br>  {<br>   // this task is for running playwright codegen<br>   &quot;type&quot;: &quot;npm&quot;,<br>   &quot;script&quot;: &quot;codegen&quot;,<br>   &quot;path&quot;: &quot;src&quot;,<br>   &quot;label&quot;: &quot;Open Playwright codegen&quot;,<br>   &quot;detail&quot;: &quot;npx playwright codegen appName.com&quot;,<br>  },<br>  {<br>    // Besides referencing npm script, you can also run any shell scripts<br>    // For example, this task can be used to open a hosts file for editing<br>    &quot;label&quot;: &quot;Update host file&quot;,<br>    &quot;type&quot;: &quot;shell&quot;,<br>    &quot;command&quot;: &quot;cd /c/Windows/System32/drivers/etc/ &amp;&amp; pwd &amp;&amp; vim hosts&quot;,<br>  },<br>  {<br>    // this task is used to flush dns using a command prompt<br>    &quot;label&quot;: &quot;Flush DNS&quot;,<br>    &quot;type&quot;: &quot;shell&quot;,<br>    &quot;command&quot;: &quot;ipconfig /flushdns&quot;,<br>    &quot;presentation&quot;: {<br>        &quot;reveal&quot;: &quot;always&quot;<br>    },<br>    &quot;windows&quot;: {<br>        &quot;options&quot;: {<br>            &quot;shell&quot;: {<br>                &quot;executable&quot;: &quot;cmd.exe&quot;,<br>                &quot;args&quot;: [&quot;/d&quot;, &quot;/c&quot;]<br>            }<br>        }<br>    }<br>  }<br> ]<br>}</pre><p>Now, to run any of these tasks, first open VSCode Command Palette (command + p) on mac, and you should see this screen and then click on “Tasks: Run Task”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m-8Ojn-zTZQWurrDMAHWkQ.png" /><figcaption>VSCode Command Palette</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gkWx7a2nurOkg5P8jjJMMw.png" /><figcaption>VSCode Command Palette showing list of tasks we defined in the tasks.json file</figcaption></figure><p>Now you can click on any of the task and it will get executed. To make it even easier, we can also install a new VSCode extension called “Tasks”. This will make running any of these tasks a one click step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*a2IVVUwnfFzFJ4fhasBwYg.png" /><figcaption>VSCode Tasks extension</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5agZqF6Zcf3Aty5Q6t8Iog.png" /><figcaption>Each of the tasks we defined now show up as a button</figcaption></figure><p>In conclusion, VSCode tasks offer a compelling and efficient way to automate repetitive or complex tasks within your development workflow. By integrating directly with tools like NPM, they bridge the gap between your IDE and build systems, leading to a smoother, more streamlined development experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a75e40e0f0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>