search

angular / angular2-seed

MIT License
1.01k stars 639 forks source link

Question: main idea behind the WebPack config split? #108

Closed pkozlowski-opensource closed 7 years ago

pkozlowski-opensource commented 8 years ago

@gdi2290 currently in our webpack.config.js we've got 2 config blogs that get merged later on:

It is not immediately clear for me why this split exists and what is the added value of it. Could we potentially get rid of this split? Or are you seeing this as something essential?

PatrickJS commented 8 years ago

the idea was to provide a simple version of webpack config that the developer can focus on while a lot of the edge cases devs ran into in angular2-webpack-starter were covered in the default config.

resolve.extensions, node and output.filename can be moved up and you can remove the webpack-merge. the watchOptions are there for anyone who is running the starter in a vm where it's not obvious that it will reload. historyApiFallback is there for when a dev uses push5 in the router and doesn't know how to add it to the dev server. debug, cache, devtool can be removed