Opening vscode via vscode-recent makes vscode 'forget' node on commit

[WandersonAlves]

trafficstars

When making a commit using vscode Source Control tab, vscode complains about node

The error:

> git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -
Yarn requires Node.js 4.0 or higher to be installed.
husky - pre-commit hook exited with code 1 (error)

Using the internal terminal works. Only on Source Control tab this problem occurs.

Some info:

➜ which code    
/usr/bin/code

[mattalxndr]

@WandersonAlves This seems like a problem with VS Code. Are you saying that the problem only occurs when you use Ulauncher to open the file?

[WandersonAlves]

Yes, if open my projects in the old way (cd into folder and code .) source control works as expected. If a open via ulauncher, vscode complains about node (only on source code tab). Internal terminal works as expected in both scenarios