Update the Concepts section with webpack v4 configuration

[jeremenichelli]

In the Concepts section we still have old config snippets and we also are not reflecting the fact that webopack is now zero config out of the box.

Some content might also need to be change so it's compatible with the new webpack default behavior.

[arjendeblok]

Also the home page of the web site still reflects that you need a config file. Should be changed too.

[jeremenichelli]

Yeap. From above:

we also are not reflecting the fact that webopack is now zero config out of the box.

[EugeneHlushko]

@jeremenichelli u on it or i can pick up both concepts configuration and homepage?

[jeremenichelli]

Go for it @EugeneHlushko! Assign the issues to yourself so we don't overlap (this one and the homepage and configuration).

Here's a list of things to needed actions on the config files or possible warnings:

• update node.js to 8
• install webpack-cli
• upgrade loaders and pluginsConfig
• add mode: "development"/"production" to config files
• remove DefinePlugin process.env.NODE_ENV
• remove NoEmitOnErrorsPlugin/NoErrorsPlugin
• remove NewWatchingPlugin
• remove ModuleConcatenationPlugin
• remove NamedModulesPlugin
• remove CommonsChunkPlugin
• may add optimization.runtimeChunk
• may add optimization.splitChunks.chunks: "all"
• remove uglifyjs-webpack-plugin
• may add optimization.minimizer for custom objects
• module.loaders -> module.rulesCode
• when import(cjs) access the default property

They are not mandatory, just a check list for you to look at when updating the config snippets. Have fun and thanks for collaborating!

[EugeneHlushko]

@jeremenichelli there are not enough privileges i suppose to assign it on myself :(

[jeremenichelli]

Whenever you want to grab some issue just be verbose in the comment thread and I will proceed to assign it to you 😊

[EugeneHlushko]

thank you!

[EugeneHlushko]

@montogeek @jeremenichelli this seems done now, can close i guess

[tylerlong]

According to the list, I guess NamedModulesPlugin is no longer required.

But it is still mentioned in the documentation:

• https://webpack.js.org/guides/hot-module-replacement/
• https://webpack.js.org/plugins/named-modules-plugin/