Laravel-mix: How to hide webpack output result table ?

[fvsadem]

• Laravel Mix Version: 6.0.6
• Node Version: 14.15.4
• NPM Version: 6.13.7
• Webpack Version: 5.11.1
• cross-env Version: 7.0.3
• OS: Windows 10

Hi,

When i build for production with the command below, i have the webpack results in a table.
npm run production
Where script is:
cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --config=node_modules/laravel-mix/setup/webpack.config.js

How could i hide the table below and just show "Compiled Successfully in xxxx ms"

   Laravel Mix v6.0.6   


✔ Compiled Successfully in 13063ms
┌───────────────────────────────────┬──────────┐
│ File                              │ Size     │
├───────────────────────────────────┼──────────┤
│ fonts/vendor/@fortawesome/fontaw… │ 896 KiB  │
├───────────────────────────────────┼──────────┤
│ fonts/vendor/@fortawesome/fontaw… │ 730 KiB  │
├───────────────────────────────────┼──────────┤
│ /js/app.js                        │ 310 KiB  │
├───────────────────────────────────┼──────────┤
│ css/app.css                       │ 290 KiB  │
├───────────────────────────────────┼──────────┤
................................

Thanks for you help

[JeffreyWay]

I don't think we currently expose an option to hide that. You're the only person I've seen request it, so I'm not sure it's overly necessary.

[0x6d617474]

We have a logging function in our CI/CD process which has a fairly low limit on the number of bytes it stores, so having the option to disable the output table at the end would be very helpful in that case, since otherwise errors later in the CI process get hidden because the table takes up a lot of space.

In Mix 5 the output was hidden in our production deployments, and I was sad to see no option to disable it in 6.

[isotrope]

I might be the second person.

I have two .copy() processes in my build.
That means that I end up with a table that's about two screens-high of image filenames.

The previous version discarded this information and I only saw the affected files.
( It also did a clear so it was more of a status panel )

Can I, at the very least, choose "which processes" to exclude from that table?
It also doesn't say "when" it concluded so I'm never sure which of the humongous lists were the last ones when trying to scroll up (because of the lack of clearing the terminal).

[lk77]

Hello,

same issue here,

the new table is unusable, nearly 50+ rows,

every file is listed, woff2 / css / json / svg and so on

✔ Compiled Successfully in 80995ms

│/css/iconfont.css │ 12.9 KiB │
│icons/fonts/MaterialIcons-Regular.eot │ 91.6 KiB │
│icons/fonts/MaterialIcons-Regular.json │ 42.2 KiB │
│icons/fonts/MaterialIcons-Regular.ttf │ 225 KiB  │
│icons/fonts/MaterialIcons-Regular.woff │ 103 KiB  │
│icons/fonts/MaterialIcons-Regular.woff2 │ 80.6 KiB │
│icons/material-icons.css │ 98.1 KiB │
│/css/prism-tomorrow.css │ 1.72 KiB │
│/css/framework.css │ 189 KiB  │
│/fonts/MaterialIcons-Regular.woff │ 77.7 KiB │
│/fonts/brandon-grotesque-medium.otf │ 87.5 KiB │
│/fonts/feather.eot │ 60.6 KiB │
│/fonts/feather.svg │ 209 KiB  │
│/fonts/feather.ttf │ 60.5 KiB │
│/fonts/feather.woff │ 28.8 KiB │
│/js/app.js │ 1.5 MiB  │
│/js/manifest.js │ 15.5 KiB │
│/js/vendor.js │ 10.9 MiB │
│css/app.css │ 74.2 KiB │
│css/main.css │ 1.56 MiB │
│c576abad9184bbb211ea6e64eb39d2e3 │ 6.02 KiB │
│js/chunks/ag-grid.js │ 6.02 MiB │
│js/chunks/module18.js │ 3.22 MiB │
│js/chunks/module17/form.js │ 1.57 MiB │
│js/chunks/module16/index.js │ 1.04 MiB │
│js/chunks/module15/form.js │ 3.3 MiB  │
│js/chunks/module14/index.js │ 1.21 MiB │
│js/chunks/fabric.js │ 2.49 MiB │
│js/chunks/filestack.js │ 668 KiB  │
│js/chunks/module12.js │ 109 KiB  │
│js/chunks/module12b.js │ 63 KiB   │
│js/chunks/module11.js │ 1.14 MiB │
│js/chunks/module10.js │ 89.3 KiB │
│js/chunks/pdfjs-dist.js │ 1010 KiB │
│js/chunks/module9.js │ 1.11 MiB │
│js/chunks/module8/diagnostic.js │ 977 KiB  │
│js/chunks/module8/form.js │ 1.11 MiB │
│js/chunks/module8/index.js │ 945 KiB  │
│js/chunks/module8/order.js │ 1.09 MiB │
│js/chunks/module8/stat.js │ 63 KiB   │
│js/chunks/module7.js │ 119 KiB  │
│js/chunks/module6.js │ 1.16 MiB │
│js/chunks/module5/form.js │ 1.9 MiB  │
│js/chunks/module4/index.js │ 1.24 MiB │
│js/chunks/module3.js │ 20.1 KiB │
│js/chunks/module2.js │ 2.04 MiB │
│js/chunks/module1.js │ 4.16 MiB │
│pdf.worker.worker.js │ 3.4 MiB  │

[pabueco]

I had the same issue when using a package that copied a few hundred images to the public folder. Mix would just print every single file on every compilation. I invested some time since it was really annoying.

Turns out you can simply add an event hook and overwrite the assets object.

mix.after((stats) => {
  stats.compilation.assets = {}
})

This however prevents mix from displaying any files at all.
If you only want to remove unimportant files like images you can just do this.

mix.after((stats) => {
  const assets = { ...stats.compilation.assets }
  stats.compilation.assets = {}

  for (const [path, asset] of Object.entries(assets)) {
    if (path.endsWith('.js')) {
      stats.compilation.assets[path] = asset
    }
  }
})

Since you get the whole target path of the asset you can also filter them based on their destination folder or use a regex to apply a more complex filter logic.

[thecrypticace]

I'm gonna re-open this. I think showing 100s of files is overkill and we need at least some way to filter them. Also we need to investigate if we can show only changed files when watching.

[thecrypticace]

I won't have the time to put forth to this today (maybe this week?) but we'd definitely welcome a PR and I'll be more than happy to help whoever work through it.