<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Alex M</title>
    <description>The latest articles on DEV Community by Alex M (@thuragan).</description>
    <link>https://dev.to/thuragan</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F850389%2F4f8908d9-759e-4f29-a90e-ae5cd12798f1.jpg</url>
      <title>DEV Community: Alex M</title>
      <link>https://dev.to/thuragan</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/thuragan"/>
    <language>en</language>
    <item>
      <title>Enable WSL shell in GitHub Desktop</title>
      <dc:creator>Alex M</dc:creator>
      <pubDate>Thu, 29 Aug 2024 05:23:18 +0000</pubDate>
      <link>https://dev.to/thuragan/enable-wsl-shell-in-github-desktop-4b16</link>
      <guid>https://dev.to/thuragan/enable-wsl-shell-in-github-desktop-4b16</guid>
      <description>&lt;p&gt;Even though WSL shell support has been added to GitHub Desktop as far back as in &lt;a href="https://github.com/desktop/desktop/pull/7821" rel="noopener noreferrer"&gt;2019&lt;/a&gt;, the actual option is still missing from the shell list.&lt;/p&gt;

&lt;p&gt;There are two ways to enable it:&lt;/p&gt;

&lt;p&gt;1) Use GitHub Desktop Beta.&lt;/p&gt;

&lt;p&gt;2) If you are using a stable version, you need to enable preview features. Set &lt;code&gt;GITHUB_DESKTOP_PREVIEW_FEATURES&lt;/code&gt; environment variable to &lt;code&gt;1&lt;/code&gt;. You can do this in Windows PowerShell:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[Environment]::SetEnvironmentVariable("GITHUB_DESKTOP_PREVIEW_FEATURES", "1", "User")
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Restart GitHub Desktop and you should now see WSL in the shell list.&lt;/p&gt;

</description>
      <category>github</category>
      <category>wsl</category>
      <category>githubdesktop</category>
    </item>
    <item>
      <title>Unpopular opinion: Volar is a buggy mess.</title>
      <dc:creator>Alex M</dc:creator>
      <pubDate>Tue, 27 Jun 2023 16:35:30 +0000</pubDate>
      <link>https://dev.to/thuragan/unpopular-opinion-volar-is-a-buggy-mess-1feb</link>
      <guid>https://dev.to/thuragan/unpopular-opinion-volar-is-a-buggy-mess-1feb</guid>
      <description>&lt;p&gt;I love Vue and the concept of SFCs - but SFCs have a downside of DX tooling around it, and there is only one de-facto tool for it - Volar.&lt;/p&gt;

&lt;p&gt;I have used Volar since its inception when it succeeded Vetur and watched it grow over the years. Unfortunately, these were painful years not without some hair-pulling moments.&lt;/p&gt;

&lt;p&gt;My biggest gripe with Volar's development was the amount of breaking changes between each release. Every time a VSCode extension would auto-update, something would break; even more so if you used any of the Volar plugins for &lt;code&gt;.vue&lt;/code&gt; file formatting such as &lt;code&gt;volar-plugins/prettier&lt;/code&gt;. While I was chasing the latest versions, I have personally filed many issues on GitHub, some of which have been fixed but ultimately it was eating into my development time and I could no longer afford to do that. I have since stopped auto-updating the extension or any of dependencies.&lt;/p&gt;

&lt;p&gt;My current setup includes an extension and dependencies that are 7 months old, and it works as expected. There were so many major version updates since then, that I've recently tried to update to it - with a predicted result: it broke formatting. Back to my old versions I go.&lt;/p&gt;

</description>
      <category>vue</category>
      <category>volar</category>
    </item>
  </channel>
</rss>
