No way to specify webpack 4 "mode" in WebpackDevMiddlewareOptions? #1595

Activity

1. bharney commented on Mar 29, 2018

   

   bharney

   on Mar 29, 2018

   More actions

   I handled it by just setting mode in both webpack.config files. Below is what I have in the shared portion of each config file.

   const sharedConfig = () => ({
           mode: isDevBuild ? 'development' : 'production',
           stats: { modules: false },
   

   That cleared the warning up for me without much change to the configuration. Hope this helps!

   👍React with 👍1Reacted by Paul Somarriba
2. salixzs commented on Apr 1, 2018

   

   salixzs

   on Apr 1, 2018

   More actions

   To update to WebPack 4, --mode should be specified somehow always, so it may ask for some more drastic changes in all JavaScriptServices and/or middlewares.

   --mode development will not do uglifying, map-ing, bundling, cherry-picking and other things it now does automatically for --mode production­. And moreover - production mode now is default (if not speficied). Could be good if JavaScript services could be updated to support Webpack 4, so we get development more goodness with it. As additional - webpack 4 is reported to be considerably faster than previous versions.

   Article on Medium.
   Another article

   On sad note - there are some popular plugins, which got broken on webpack 4, like extract-text-webpack-plugin (now has 4.0.0 alpha release).
3. SteveSandersonMS commented on Apr 3, 2018

   

   SteveSandersonMS

   on Apr 3, 2018

   Member

   More actions

   Webpack 4 support is covered by #1562
4. SteveSandersonMS

   closed this as completedon Apr 3, 2018