Do not print webpack progress output in a production build

Produces around 2000 rows less output in the production build. The progress output for a CI build is not relevant and is in the way when looking for build problems.
vaadin · May 5, 2020 · cf144b0 · cf144b0
1 parent 60da8ea
commit cf144b0
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildFrontendMojo.java b/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/BuildFrontendMojo.java
@@ -195,7 +195,7 @@ private void runWebpack() {
         }
 
         List<String> command = Arrays.asList(nodePath,
-                webpackExecutable.getAbsolutePath(), "--progress");
+                webpackExecutable.getAbsolutePath());
         ProcessBuilder builder = FrontendUtils.createProcessBuilder(command)
                 .directory(project.getBasedir()).inheritIO();
         getLog().info("Running webpack ...");

diff --git a/flow-server/src/main/resources/webpack.generated.js b/flow-server/src/main/resources/webpack.generated.js
@@ -146,7 +146,7 @@ module.exports = {
     // Generate compressed bundles when not devMode
     !devMode && new CompressionPlugin(),
     // Give some feedback when heavy builds
-    new ProgressPlugin(true),
+    devMode && new ProgressPlugin(true),
 
     // Generates the stats file for flow `@Id` binding.
     function (compiler) {