[checkmk-commits] [tribe29/checkmk] eeebff: Use Webpack's production mode by default, shipping...

Branch: refs/heads/1.6.0 Home: https://github.com/tribe29/checkmk Commit: eeebff9def341d2f106b52f27b93f797ac4fac2d https://github.com/tribe29/checkmk/commit/eeebff9def341d2f106b52f27b93f797a… Author: Sven Panne <sven.panne(a)tribe29.com> Date: 2019-09-06 (Fri, 06 Sep 2019) Changed paths: M Makefile M web/.f12 M webpack.config.js Log Message: ----------- Use Webpack's production mode by default, shipping minified JavaScript. You can choose the way Webpack will run via the environment variable WEBPACK_MODE, giving you a choice between deployment speed, portability and runtime speed: * quick: Run Webpack in development mode and don't run Babel. This means that JavaScript does not get transpiled, so you need a very recent browser. Minification is not done. * development: Run Webpack in development mode, including Babel. JavaScript is being transpiled, but not minified. * production: Run Webpack in production mode, including Babel. JavaScript is transpiled and minified. The top-level Makefile uses "production" by default, and web/.f12 uses "development" by default. You can override this by setting the WEBPACK_MODE environment variable if you want. Note that the way we configure and run Webpack is quite a hack, we should really clean this up, see e.g. https://webpack.js.org/guides/production/. Furthermore, we should split our JavaScript files and improve the way when we build what: Currently we e.g. rebuild all our JavaScript stuff when some tiny CSS file has changed. :-/ Change-Id: I08db2fefa7ba4abe1fe27815dfe5bc90db8f365f