

This really helps us to achieve good performance by build timing. For example for dev build we do not minimize and do not type check our code. And put different kind of logic in accordance with puproses for each build. So we've separated our webpack config on 3 peaces: common, dev, prod. TranspileOnly: true // NO typecheck for DEV buildĮxample of config for creating PROD package on remote server: const merge = require('webpack-merge') const merge = require('webpack-merge') Ĭonst common = require('./').config Īctually this config could be very big and very common depends on your purposes. "": path.resolve(_dirname, "scripts/kendo-ui-forked/js/"),Įxtensions: , "kendo-ui-angular": path.resolve(_dirname, "scripts/kendo-ui-forked/js/"), Let's create 3 webpack configs: // list of including packages here

Let's do it!įor merge webpack config files we will use webpack-merge plugin. Of course this is one of example which you can apply on your project. So it's a good thing to separate build for typechecking and without it.
HOW TO RUN WEBPACK SERVER HOW TO
How to separate your Webpack configs? May 17, 2019
