title: Yeoman Angular dev environment with socket.io.js and NodeJS
body: <p>I've got an angular app created with Yeoman that is working well in dev, on port 9000.</p>
  
  <p>I've got a server-side node.js app running on port 3000. </p>
  
  <p>I've installed socket.io on the NodeJS application.</p>
  
  <p>Most of the JS in my angular app is in the <code>app</code> directory, but the socket.io.js is served up via node:</p>
  
  <pre><code>&lt;script src="components/angular/angular.js"&gt;&lt;/script&gt;
  &lt;script src="components/angular-resource/angular-resource.js"&gt;&lt;/script&gt;
  &lt;script src="components/angular-cookies/angular-cookies.js"&gt;&lt;/script&gt;
  &lt;script src="components/angular-sanitize/angular-sanitize.js"&gt;&lt;/script&gt;
  &lt;script src="http://localhost:3000/socket.io/socket.io.js"&gt;&lt;/script&gt;
  </code></pre>
  
  <p>This feels kind of wrong to me. Also, when I load socket.io and call <code>connect()</code> on the client side, it is trying to connect to localhost:9000, instead of localhost:3000</p>
  
  <p>Is there a way to reconcile these two worlds? Do I need to serve my angular application from within node.js? I'm reluctant to lose live reloading.</p>