Webpack

https://www.youtube.com/watch?v=GU-2T7k9NfI
https://www.sitepoint.com/bundle-static-site-webpack/
https://webpack.github.io/docs/tutorials/getting-started/ - printed
https://medium.com/@dabit3/beginner-s-guide-to-webpack-b1f1a3638460#.xv6x6zdi4 - printed
https://scotch.io/tutorials/getting-started-with-webpack-module-bundling-magic - printed
https://code.tutsplus.com/tutorials/introduction-to-webpack-part-1--cms-25791 - printed
https://code.tutsplus.com/tutorials/introduction-to-webpack-part-2--cms-25911 - printed
https://angular.io/docs/ts/latest/guide/webpack.html - printed, but might need to read online
http://semaphoreci.com/community/tutorials/setting-up-angular-2-with-webpack - printed
http://www.theodo.fr/blog/2016/07/a-comprehensive-introduction-to-webpack-the-module-bundler/ - printed
https://blog.madewithlove.be/post/webpack-your-bags/ - printed
https://blog.jetbrains.com/webstorm/2015/09/debugging-webpack-applications-in-webstorm/ - printed
https://snipcart.com/blog/how-to-use-webpack-for-killer-refactoring - printed
http://blog.xebia.com/unlocking-es2015-features-with-webpack-and-babel/ - printed
http://blog.librato.com/posts/webpack - printed
https://medium.com/@housecor/browserify-vs-webpack-b3d7ca08a0a9#.678fpfsik - printed
http://christianalfoni.github.io/javascript/2014/12/13/did-you-know-webpack-and-react-is-awesome.html - printed
https://github.com/petehunt/webpack-howto - printed
https://vuejsdevelopers.com/2017/07/24/critical-css-webpack/
https://www.youtube.com/watch?v=zFoBYfMLUCM
http://jackhiston.com/2017/9/4/the-wonderful-world-of-webpack/

To start the webpack dev server, put:

"start": "node_modules/.bin/webpack-dev-server --inline --colors 
  --display-error-details --display-cached --host 127.0.0.1"

in to the scripts section of the package.json file, and start it with:

npm start

We can also serve our application from the build directory using http-server:

npm install -g http-server
http-server app/__build

What does Webpack do for us?

Here’s a short list of things that Webpack made significantly easier for us:

  1. No more long “manifest” files that include all of our modules in a delicate and fragile order. (The same applies to our karma.config.js because of karma-webpack.)
  2. It’s no longer difficult to determine exactly what dependencies any of our internal modules have, because they’re required at the beginning of the file.
  3. It forces modularity and gives us a nice set of conventions for how to actually build things. Webpack has good documentation and it allows us to remove homegrown solutions which varied project to project.
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License