Updates dependencies, modernises the build config, and reduces repetition of config.
Note that modules can still use the old config format, which will be useful for projects and third-party modules who want to make minimal changes, but the *WebpackConfig classes handle a lot of the boilerplate which makes it easier for us to make wide-sweeping changes later down the line if we want/need to (e.g. if webpack changes the syntax for some of the config, we just need to change it in this library).
Updates dependencies, modernises the build config, and reduces repetition of config.
Note that modules can still use the old config format, which will be useful for projects and third-party modules who want to make minimal changes, but the
*WebpackConfig
classes handle a lot of the boilerplate which makes it easier for us to make wide-sweeping changes later down the line if we want/need to (e.g. if webpack changes the syntax for some of the config, we just need to change it in this library).Parent issue