title: A guideline to building angular apps based on npm and typescript
body: <p>with the release of angular2 I actually encountered typescript, npm, ... for the first time, and I really appreciate its power, so I barely grasp the surface.</p>
  
  <p>In the "development mode" I can find my way, but in the end:</p>
  
  <h2> Question: </h2>
  
  <p><em>I want to generate an independent folder that includes all necessary dependencies: js, css, html-files and is portable without needing npm, transpilers,... anymore. (So basically I want to copy this generated folder to a server and people can access the index.html as usually)</em></p>
  
  <h2> Problem </h2>
  
  <h3>Setup</h3>
  
  <ul>
  <li>npm (as a module manager and build tool) <a href="http://blog.keithcirkel.co.uk/how-to-use-npm-as-a-build-tool/" rel="nofollow">npm as a build tool</a>, <a href="http://www.sitepoint.com/guide-to-npm-as-a-build-tool/" rel="nofollow">npm as a build tool II</a></li>
  <li>typescript (tsc as transpiler)</li>
  <li>angular2 (with separated files for html, css), SystemJS</li>
  </ul>
  
  <h3>Needed Guideline</h3> 
  
  <ul>
  <li>An (abstract) guideline for what steps to take in order to achieve the prescribed goal, namely a folder that has (all) the features and is build from the typescript files, (probably .scss-files,...) in a separate and self-contained way.</li>
  </ul>
  
  <p><em>Probably I am searching for the wrong keywords but I have only found some fractions of my answers so far and I would really appreciate a list (of tutorials, or so) that I can stepwise go through. (Currently I feel lost)</em></p>