<?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: Farrukh Saeed</title>
    <description>The latest articles on DEV Community by Farrukh Saeed (@_farrukh_saeed_).</description>
    <link>https://dev.to/_farrukh_saeed_</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%2F3849244%2F6992609c-6cb0-4637-ac1b-5f91568e0bb3.jpg</url>
      <title>DEV Community: Farrukh Saeed</title>
      <link>https://dev.to/_farrukh_saeed_</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/_farrukh_saeed_"/>
    <language>en</language>
    <item>
      <title>Fixing PowerShell Execution Policy Errors for Node.js &amp; TypeScript</title>
      <dc:creator>Farrukh Saeed</dc:creator>
      <pubDate>Sun, 29 Mar 2026 13:11:47 +0000</pubDate>
      <link>https://dev.to/_farrukh_saeed_/fixing-powershell-execution-policy-errors-for-nodejs-typescript-3il7</link>
      <guid>https://dev.to/_farrukh_saeed_/fixing-powershell-execution-policy-errors-for-nodejs-typescript-3il7</guid>
      <description>&lt;p&gt;A Developer's Quick Guide to Setting Up a Seamless Windows Environment for TypeScript and NodeJS.&lt;/p&gt;

&lt;p&gt;Every developer hits this wall eventually: You try to run an npm script or the TypeScript compiler (tsc), and PowerShell greets you with a red block of text saying "Scripts are disabled on this system." Even worse, you try to fix it, and you get an "Access to the registry key is denied" error.&lt;/p&gt;

&lt;p&gt;🔍 The Problem&lt;br&gt;
By default, Windows restricts script execution for security. When you try to change the LocalMachine policy without high-level Admin rights, the system blocks you from touching the Registry.&lt;/p&gt;

&lt;p&gt;✅ The Solution&lt;br&gt;
You don't need to fight the "LocalMachine" registry. By targeting the CurrentUser scope, you can unlock your terminal immediately without needing "System" permissions.&lt;/p&gt;

&lt;p&gt;🛠️ The Ultimate Setup Checklist&lt;br&gt;
Copy and paste these commands into your VS Code terminal to get everything running smoothly.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Unlock Script Execution (The "Access Denied" Fix)
Run this first to allow npm and tsc to run:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Set-ExecutionPolicy RemoteSigned -Scope CurrentUser -Force&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Verify Your Environment
Now that the path is clear, check your versions to ensure everything is linked correctly:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;node -v — Checks Node.js version&lt;/p&gt;

&lt;p&gt;npm -v — Checks Node Package Manager version&lt;/p&gt;

&lt;p&gt;tsc -version — Checks TypeScript Compiler version&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Global TypeScript Installation
If tsc isn't recognized yet, install it globally:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;npm install -g typescript&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Fresh Project Initialization
Start your TypeScript journey with these two essentials:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;npm init -y — Creates your package.json&lt;/p&gt;

&lt;p&gt;tsc --init — Creates your tsconfig.json&lt;/p&gt;

&lt;p&gt;💡 Pro-Tip for New Developers&lt;br&gt;
If you are still seeing the error after running the commands, restart VS Code. The terminal needs a fresh start to "see" the new permissions you just granted it.&lt;/p&gt;

&lt;h1&gt;
  
  
  WebDevelopment #TypeScript #NodeJS #ProgrammingTips #CodeNewbie #WindowsDev
&lt;/h1&gt;

</description>
      <category>beginners</category>
      <category>node</category>
      <category>tutorial</category>
      <category>typescript</category>
    </item>
  </channel>
</rss>
