title: Command not found
body: <p>I'm running into a problem with accessing Yeoman after installing it on a fresh Homestead installation. Everything seems fine during the install after <code>npm install -g yo</code> and <code>yo doctor</code> runs just fine and finds no problem during the installation. However, after I've installed yeoman, <code>yo: command not found</code> is the error message I'm getting on my VM.</p>
  
  <pre><code>vagrant@homestead:~$ npm install -g yo
  npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
  /home/vagrant/.node/bin/yo -&gt; /home/vagrant/.node/lib/node_modules/yo/lib/cli.js
  /home/vagrant/.node/bin/yo-complete -&gt; /home/vagrant/.node/lib/node_modules/yo/lib/completion/index.js
  
  &gt; spawn-sync@1.0.15 postinstall /home/vagrant/.node/lib/node_modules/yo/node_modules/spawn-sync
  &gt; node postinstall
  
  
  &gt; yo@1.8.4 postinstall /home/vagrant/.node/lib/node_modules/yo
  &gt; yodoctor
  
  
  Yeoman Doctor
  Running sanity checks on your system
  
  ✔ Global configuration file is valid
  ✔ Node.js version
  ✔ No .bowerrc file in home directory
  ✔ No .yo-rc.json file in home directory
  ✔ npm version
  ✔ NODE_PATH matches the npm root
  
  Everything looks all right!
  /home/vagrant/.node/lib
  └─┬ yo@1.8.4
    ├── async@1.5.2
    ├─┬ chalk@1.1.3
    │ ├── ansi-styles@2.2.1
    │ ├── escape-string-regexp@1.0.5
    │ ├── has-ansi@2.0.0
    │ ├── strip-ansi@3.0.1
    │ └── supports-color@2.0.0
    ├── cli-list@0.1.8
  [[REMOVED FOR READABILITY]]
    └─┬ yosay@1.2.0
      ├── cli-boxes@1.0.0
      ├── pad-component@0.0.1
      ├─┬ taketalk@1.0.0
      │ ├── get-stdin@4.0.1
      │ └── minimist@1.2.0
      └── wrap-ansi@2.0.0
  
  vagrant@homestead:~$ yo
  yo: command not found
  </code></pre>
  
  <p>My path in <code>~/.bashrc</code> says the following: <code>PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/home/vagrant/.node/lib</code></p>
  
  <p>Is there anything else that I'm missing here that might be causing this?</p>