title: Is it bad practice to build the server API as part of a brunch application?
body: <p>I am using <a href="http://brunch.io" rel="nofollow">brunch</a> to build a single-page web application. The application talks to an backend CRUD API that I would like to write using node.js/express. The natural thing to me seems to be to build out the server in a subdirectory of my application, parallel to <code>app</code>. This has the advantage of having all of the code under one roof as well has allowing me to start everything up via <code>brunch watch --server</code>.</p>
  
  <p>I started doing this and then I became worried. If I have server-side dependencies that I install via <code>npm install --save-dev some-server-dependency</code>, do these dependencies get embedded into the javascript of my single-page application? This seems like it would unnecessarily increase the size of my app. If this doesn't happen, how does brunch know what dependencies to include in <code>vendor.js</code>?</p>
  
  <p>This leads to more general questions: Is it bad practice to develop the API in the same project as the client code? If so, are there any <code>brunch</code> equivalents for building the server-side API?</p>