VSCODE build error `The terminal process "/bin/zsh '-c', 'yarn run watch-extensionsd'" failed to launch (exit code: 127).`

Question

I want to build VSCode from source and I get this error:

The terminal process "/bin/zsh '-c', 'yarn run watch-extensionsd'" failed to launch (exit code: 127).

Hi, do you use MacOs or Linux with zsh? Is yarn installed? Do you have the script "watch-extensionsd' (including the d at the end) in the package.json? — Markus Madeja, Aug 20 '20 at 09:38
@MarkusMadeja MacOS and yarn is installed and it is in the package.json — Ofsho, Aug 20 '20 at 09:51

Eric Kim · Answer 1 · 2020-12-15T10:40:38.800

The problem is your npm scripts in vscode is started with /bin/zsh -c (non-login non-interactive) This means scripts inside ~/.zshrc is not executed (and for the same reason ~/.zprofile). However, even in non-login non-interactive mode, ~/.zshenv is loaded.

Solution 1:

Change "npm.packageManager": to npm
Make sure you restart vscode to make this take into effect.

Solution 2 (preferred):

Open ~/.zshrc and move whatever scripts that is loading yarn into ~/.zshenv

In my specific case, my yarn is installed through npm npm i -g yarn and my npm is installed through nvm. So I had to move following two lines.

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm

Solution 3:

Don't use VSCode's npm scripts. You can actually execute by opening terminal yourself shortcut ctrl + ` and typing out yarn "npm script name".

create a ```~/.zshenv``` add a line ```source ~/.zshrc``` – probhonjon Mar 08 '21 at 04:52 — probhonjon, Mar 08 '21 at 04:52
solution 2 works like a charm on linux, thank you – The Developer Feb 22 '22 at 08:01 — The Developer, Feb 22 '22 at 08:01

FradSer · Answer 2 · 2021-04-07T10:31:18.350

11

In my case, running on macOS:

Spotted the inheritEnv option in VS Code setting.

OR

In settings.json, add this string: "terminal.integrated.inheritEnv": false

edited Apr 07 '21 at 10:31

answered Feb 01 '21 at 05:15

FradSer

199
1
9

1

Thanks! This works for me for a similar problem! – Jun Tian Feb 08 '21 at 10:06
3

Would you please elaborate your answer? In settings.json, add this string: "terminal.integrated.inheritEnv": false – DannyThunder Mar 10 '21 at 15:40

score 6 · Answer 3 · answered Jan 11 '23 at 00:42

Related to the above, if macOS and your computer recently restarted on its own (e.g., kernel panic), I found that VScode reloads improperly without loading the environment in all Terminals that were open prior.

The fix is simply to close out of VSCode completely, then relaunch. The environments will then load properly.

score 3 · Answer 4 · answered Mar 18 '22 at 07:57

It happens that ~/.zshrc is not sourced when VS Code is launched from the application menu but if it is launched from a terminal it works perfectly. So what I did is, I changed the command of Exec field in the desktop entry file (/usr/local/applications/code.desktop or ~/.local/share/applications/code.desktop) to zsh -c "source $HOME/.zshrc && code".

score 0 · Answer 5 · answered Aug 01 '23 at 18:09

0

For me, its happening to me when I try to use nx plugin for VSCode. So, the only thing I needed to do is restart the VSCode. Boom! Its working again.

#ButYouDidn'tDoAnything

answered Aug 01 '23 at 18:09

ey dee ey em

7,991
14
65
121

score -2 · Answer 6 · answered Mar 18 '21 at 13:44

-2

In my case,
I just commented out a setting in VS Code. It works.

"files.exclude": {
  "node_modules/": true
},

answered Mar 18 '21 at 13:44

VicoHu

1

This above did not work for me. – darul75 Nov 16 '21 at 12:41

VSCODE build error `The terminal process "/bin/zsh '-c', 'yarn run watch-extensionsd'" failed to launch (exit code: 127).`

6 Answers6

Linked