Hey there! Let's work through this issue step by step—you've already checked the basics, so we'll target the common pitfalls that might be blocking you from using Yarn.

1. Correct the Environment Variable Path #

You mentioned adding C:\Users\**path**\AppData\Roaming\npm\node_modules\yarn\bin to your PATH, but that's not the right directory. When you install Yarn globally via npm, the executable shortcuts are linked directly to your npm global bin folder:
C:\Users\vdine\AppData\Roaming\npm

Your installation output confirms this:

C:\Users\vdine\AppData\Roaming\npm\yarn -> C:\Users\vdine\AppData\Roaming\npm\node_modules\yarn\bin\yarn.js
C:\Users\vdine\AppData\Roaming\npm\yarnpkg -> C:\Users\vdine\AppData\Roaming\npm\node_modules\yarn\bin\yarn.js

Replace the path you added with C:\Users\vdine\AppData\Roaming\npm in your environment variables.

2. Check Where You Added the Path #

Ensure you're adding the path to the correct section of environment variables:

• For just your user account, add it to User variables > PATH
• For all users on the machine, add it to System variables > PATH

Placing the path early in the list can also avoid conflicts with other tools, though this is rarely necessary for Yarn.

3. Restart All Terminals/IDEs #

This is a crucial step! Any terminal window (Command Prompt, PowerShell, VS Code terminal, etc.) that was open before you modified the environment variable won't pick up the new path. Close every open terminal and IDE, then reopen them to test yarn --version.

4. Verify the Path is Active #

To confirm the path is loaded correctly:

• In Command Prompt, run:

  echo %PATH%
  

• In PowerShell, run:

  $env:PATH
  

Look for C:\Users\vdine\AppData\Roaming\npm in the output. If it's missing, double-check your environment variable edits.

5. Test the Executable Directly #

Navigate to C:\Users\vdine\AppData\Roaming\npm in File Explorer. You should see yarn.cmd (for Command Prompt) and yarn.js (for Node.js). Open a terminal in this folder and run:

yarn --version

If this works, the issue is definitely with your environment variable not being applied. If it fails, your Yarn installation might be corrupted.

6. Clean Reinstall Yarn (If Needed) #

If the direct test fails or the path still isn't working, try a fresh install:

1. Uninstall Yarn globally:

   npm uninstall yarn -g
   

2. Clear npm's cache to remove corrupted files:

   npm cache clean --force
   

3. Reinstall Yarn:

   npm install yarn -g
   

4. Repeat steps 2-4 to verify the path and restart your terminal.

内容的提问来源于stack exchange，提问作者Dinesh Veera