title: How to solve $PATH not resolving in VSCode
body: <p>After recent upgrade of <code>Fedora 30 -&gt; Fedora 31</code> I'm observing that when I launch a terminal from within VSCode for the project that I'm working on, I see this message:</p>
  <pre class="lang-sh prettyprint-override"><code>bash: sed: command not found
  ~/data/Programming/JS/React vgorcinschi $ 
  </code></pre>
  <p>It is complaining about <code>sed</code> because I have a script in <code>~/.bashrc</code> that tries to include in <code>PS1</code> information about git branches:</p>
  <pre class="lang-sh prettyprint-override"><code># somewhere in ~/.bashrc
  parse_git_branch() {
       git branch 2&gt; /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/ (\1)/'
  }
  export PS1=&quot;\[\033[32m\]\w\[\033[33m\]\$(parse_git_branch)\[\033[00m\] \u $ &quot;
  </code></pre>
  <p>If, within the same terminal, I do <code>man sed</code> it will complain in the same manner about <code>man</code>. If I open a system terminal and navigate to the same location my path would look like this:</p>
  <pre class="lang-sh prettyprint-override"><code>~ vgorcinschi $ cd ~/data/Programming/JS/React
  ~/data/Programming/JS/React (ch14) vgorcinschi $ echo $PATH
  ./node_modules/.bin:/home/vgorcinschi/.nvm/versions/node/v10.6.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/vgorcinschi/.local/bin:/home/vgorcinschi/bin:/home/vgorcinschi/.local/bin:/home/vgorcinschi/bin:/usr/local/java/jdk1.8.0_231/bin:/opt/maven/bin:/snap/bin
  </code></pre>
  <p>NB Note how sed works from within the same directory.</p>
  <p>Repeating <code>echo $PATH</code> from VS Code terminal yields just this: <code>/home/vgorcinschi/data/Programming/JS/React/node_modules/.bin</code></p>
  <p>I think this question may come-up so these are the contents of my <code>~/.config/Code/User/settings.json</code>:</p>
  <pre><code>{
      &quot;git.enableSmartCommit&quot;: true,
      &quot;metals.javaHome&quot;: &quot;/usr/local/java/jdk1.8.0_231&quot;,
      &quot;window.zoomLevel&quot;: 0,
      &quot;terminal.integrated.shell.linux&quot;: &quot;/usr/bin/bash&quot;,
      &quot;editor.tabSize&quot;: 2,
      &quot;editor.detectIndentation&quot;: false,
      &quot;terminal.external.linuxExec&quot;: &quot;bash&quot;
  }
  </code></pre>
  <p>The following could also be very important. The directory above is on a partition which is on HDD (<code>/dev/sdb1</code>) , my <code>~/.bashrc</code> and <code>~/.bash-profile</code> are on a SSD (<code>/dev/mapper/fedora-home</code>).</p>
  <p>If I open an empty directory with VS Code on the main partition (on SSD) I don't have this issue with the Code's terminal. But I didn't have it on the other partition either before the upgrade - this was just two days ago.</p>
  <p>So I am not sure what is the issue really due to, but hopefully someone could help me with it.</p>
  <p><strong>Update [2020.10.30]</strong>
  <code>.node_modules</code> appear on the path inside VSCode terminal because of these lines in <code>~/.bashrc</code>:</p>
  <pre class="lang-sh prettyprint-override"><code>if [ -d &quot;$PWD/node_modules/.bin&quot; ]; then
          PATH=&quot;$PWD/node_modules/.bin&quot;
  fi
  
  </code></pre>
  <p>VS Code version</p>
  <pre class="lang-sh prettyprint-override"><code>Version: 1.50.1
  Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
  Date: 2020-10-13T14:44:48.716Z
  Electron: 9.2.1
  Chrome: 83.0.4103.122
  Node.js: 12.14.1
  V8: 8.3.110.13-electron.0
  OS: Linux x64 5.8.15-101.fc31.x86_64
  </code></pre>