This repository has been archived by the owner on May 29, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 512
Log Spam #97
Comments
From #35, this worked for me: module.exports = {
stats: { children: false },
// other settings
} |
nylen
added a commit
to redmountainmakers/kilntroller-ui
that referenced
this issue
Aug 7, 2016
Dev mode: list of 486 modules included in chunk Production mode: 8 of these: Child extract-text-webpack-plugin: + 2 hidden modules References: - webpack-contrib/extract-text-webpack-plugin#97 - http://webpack.github.io/docs/node.js-api.html#stats - https://github.com/webpack/webpack/blob/v1.13.1/lib/Stats.js
ryardley
added a commit
to ryardley/seek-style-guide
that referenced
this issue
Feb 14, 2017
Extract text plugin was spamming the output with "Child extract-text-webpack-plugin: + 19 hidden modules" 30 odd times. This fix surpresses those log reports. reference webpack-contrib/extract-text-webpack-plugin#97
Please reopen this bug. It is not adequate to just hide stats from all children. If a config is sent as an array, there will be no output at all then. |
@d3viant0ne Hey, this is still a bug. As already mentioned, the workaround is not adequate. |
Here's a simple webpack plugin I use that does the job of cleaning up the log spam. But I agree that it should be configurable within class CleanUpStatsPlugin {
/**
* @param {Object} child
* @param {string} child.name
* @returns {boolean}
*/
shouldPickStatChild(child) {
return child.name.indexOf('extract-text-webpack-plugin') !== 0;
}
apply(compiler) {
compiler.plugin('done', stats => {
if (Array.isArray(stats.compilation.children)) {
stats.compilation.children = stats.compilation.children.filter(child => this.shouldPickStatChild(child));
}
});
}
}
module.exports = CleanUpStatsPlugin; |
@le0nik I hope you don't mind that I published your code as a package on npm's registry: |
You can also call |
Please set Example:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For every file this plugin extracts, it prints a meaningless message into the stdout.
I just started on a project with this integrated and i already have a wall of:
Is there a way to silence this plugin?
The text was updated successfully, but these errors were encountered: