Merge branch 'webpack'

Conflicts:
	README.md

Author: Vlad Sternbach

README.md

@@ -47,7 +47,6 @@ Now browse to the app at `http://localhost:8080/`.
 
 ```
 src/                    --> all of the source files for the application
-  app.css               --> default stylesheet
   components/           --> all app specific modules
   services/                --> all app common services
   assets/                --> all of the app static assets
@@ -63,18 +62,8 @@ Typescript development is dependant on typings project, that need to be installe
 sudo npm install -g typings
 ```
 
-The angularjs-typescript-webpack project comes preconfigured with a local development webserver.  It is a webpack-dev-server, that supports hot reload.  You can start this webserver with `npm start`.
+The angularjs-typescript-webpack project comes preconfigured with a local development webserver. It is a webpack-dev-server, that supports hot reload.  You can start this webserver with `npm start`.
 
-### Running the App in Production
+### Building and running the App in Production
 
-This really depends on how complex your app is and the overall infrastructure of your system, but
-the general rule is that all you need in production are all the files under the `app/` directory.
-Everything else should be omitted.
-
-Angular apps are really just a bunch of static html, css and js files that just need to be hosted
-somewhere they can be accessed by browsers.
-
-If your Angular app is talking to the backend server via xhr or other means, you need to figure
-out what is the best way to host the static files to comply with the same origin policy if
-applicable. Usually this is done by hosting the files by the backend server or through
-reverse-proxying the backend server(s) and webserver(s).
+To build the application for production just run `npm bundle`, it creates dist directory that have the production optimized build.