pnpm command not recognized (VS Code)

[sillvva]

I've installed pnpm on Windows. The command works in Windows PowerShell Terminal, but I can't get it to work in VS Code PowerShell Terminal. I've tried removing the terminal and making a new one, restarting VS Code, updating VS Code. The command is still not recognized.

pnpm: The term 'pnpm' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

I couldn't find anything in Google search, Bing Search, or Github search to resolve the issue.

[sillvva]

Nevermind. I used the standalone script install. It worked after using npm install method.

[woss]

i don't think that's a correct answer, this is just another way to install the pnpm.

the correct answer is, that you should have added the pnpm binary to the path. and it seems you are using windows which requires you to either use the generally accepted paths which are included in the environment or manually set up the directory where you store the custom binaries that are included in the env.

[Fred-Vatin]

Actually, the standalone script should automatically add the pnpm directory to the path. This script:

iwr https://get.pnpm.io/install.ps1 -useb | iex

It does. %PNPM_HOME% is added to the path. It works when using pnpm in the Windows terminal but not in VSCode terminal. Using the same powershell version, it then returns : The term 'pnpm' is not recognized as a name of a cmdlet...

I tried to play with VSCode settings and succeeded to fix this issue :

"terminal.integrated.profiles.windows": {
  "PowerShell": {
	  "path": "pwsh",
	  "icon": "terminal-powershell",
  },
},
"terminal.integrated.env.windows": {
  "PATH": "${env:PATH};${workspaceFolder}\\node_modules\\.bin;${env:PNPM_HOME}"
},

You may need to restart VSCode after adding these settings.

EDIT: as the current version 1.95, I recommend to delete the "terminal.integrated.env.windows" settings because if ${workspaceFolder} doesn't exist, ${env:PATH} is not substituted. See #212062 which has not been fixed as it is said.

[HarshAggarwals]

Thank you so much @Fred-Vatin, your solution resolved my issue. Adding these setting in package.json, make vs recognize pnpm command

[wildrap]

It does not create folders on app/local but the pnpm are in app/roaming even with the env on it. it still does not work

[hotsu0p]

I just needed to restart vs code

[azmek]

a simple restart of vs code resolved the issue

[privatenumber]

I'm on a fresh copy of Windows 11 Enterprise (Evaluation) via VirtualBox and I was able to work around this by copying the PNPM_HOME User variable to System variable.

[g8up]

I change the "PNPM_HOME" to lowercase "pnpm_home", and so is the refer "%pnpm_home%" in Path. It works.
I don't know why.

[immortal-blog]

This workes for me! Thank you.

[valdemirum]

Added %PNPM_HOME% to the system Path variable and it worked!

[Sameqdev2]

Funcionou perfeitamente, obrigado cara, que Deus te abencoe

[c4nzin]

Thanks!

[bipulmgr]

First, use pnpm standalone script. It will worked.
https://pnpm.io/installation

If that didn't work then copy pnpm.exe file from

C:\Users\hp\AppData\Local\pnpm

folder and paste it into

C:\Program Files\nodejs

folder.

[ashwth]

Windows 11 here. I have used the standalone script to install it. In my case restarting all instances of vs code solved the problem.

[kevinkirsten]

worked for me too, thanks!

[EvilChan]

Replace in "Path" "%PNPM_HOME%" explicit with "%PNPM_HOME%\".
Press Ok, check powershell and it should be fixed.

[teocto]

@Fred-Vatin thank you !!!

[marcus-evans]

Here's the proposed solution on handling this issue

1. First check the execution policy for the current user .
   Please copy the code below and execute this on your vscode terminal

Get-ExecutionPolicy -Scope CurrentUser

2. if the result is Undefined change the execution policy for current user.
   Please copy the code below and execute this on your vscode terminal

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

3. Then check if the execution policy are change to RemoteSigned

Get-ExecutionPolicy -Scope CurrentUser

If the execution is successfully changed from Undefine to RemoteSigned then you can now test your any pnpm command directly to your vscode terminal.
Sample pnpm command

pnpm --version

Resources:
Microsoft: about_Execution_Policies

[aix216]

i don't have administrator privileges.
It workes for me! Thank you very much.

[LouieGuides]

In my case, I open the powershell as admin and paste this
iwr https://get.pnpm.io/install.ps1 -useb | iex

Then Install the LTS version of Node.js
pnpm env use --global lts

Then go to the specific folder by using cd command and check node version if it was their
node -v

Done!

[zongren]

In my case, after changing vscode to run as administrator, the issue solved.

[Israr-11]

I solved the problem by opening the Power Shell as 'Administrator' and running the standalone script from pnpm's documentation.

iwr https://get.pnpm.io/install.ps1 -useb | iex

[arshad-yaseen]

This works for me ❤️

[iBz-04]

right click VSCODE and choose "run as administrator" that's all

[sharabhh]

So I went with @privatenumber method (thanks!), Go to the location in your C drive

and add the path to your system environment path variables.
Re launch VS code. It worked for me at least <3

[Zoly90]

Windows user, installed it through PowerShell, this worked for me. Untill than the pnpm folder was completly empty. So for PowerShell use this command:
Invoke-WebRequest https://get.pnpm.io/install.ps1 -UseBasicParsing | Invoke-Expression

[xyfll7]

change the file C:\Users\NAME\AppData\Local\pnpm\pnpm
to C:\Users\NAME\AppData\Local\pnpm\pnpm.exe
then is works