Provide a way to mute warnings that can only be fixed with access to configuration

Create React App doesn’t expose Webpack configuration to the users, so any Webpack warnings that require fixes in config are non-actionable for our users. Unless they are critical (but in this case they should be errors), I would like to have an option to mute them.

#1617 is a good example of such warning. Create React App users have no control over it (when caused by third party libraries shipping a pre-built file). Just adding a noParse option wouldn’t work for them because they can’t change the config. For this warning specifically, there are also some users who consciously choose to use precompiled files (e.g. for build speed), so I’m not sure it’s entirely relevant in all cases.

Another example of this being inconvenient is that this warning causes CI to fail for our users. We use eslint-loader and due to popular demand configured CI script to treat ESLint warnings as errors on CI. Unfortunately this also means unactionable Webpack warnings break the build. (facebook/create-react-app#1150)

Would you consider a feature request of muting warnings that are only actionable for people with access to the config?

Author: Fantashit

1 thought on “Provide a way to mute warnings that can only be fixed with access to configuration

  1. I have full access to a regular Webpack config, but people using my package (that builds on top of Webpack) don’t.

Comments are closed.