Option to treat warnings as errors - pure and 100% compliant production build #33312
Unanswered
ursaj
asked this question in
Ideas / Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Use-case
I'm building production site:
There is a broken link from an inner page to the renamed static image.
Expected
Actual
Scope of the problem
StaticImage
is just a single component with such behaviour. There are a lot of other components and plugins that report warnings, while still working. Sometimes incorrectly.To keep code clean and 100% compliant with all plugins/rules/checks - there should be ZERO warnings in production build output. The point is not in reporter usage (it's out of my and other users control), but how its output is interpreted.
Alternative ways
Indeed I can parse output, e.g. like described on stackoverflow, but to have this option out-of-the-box is much more convenient and simpler for integration.
PR
Default behaviour - unchanged. Those who need such strict mode - would use
FAIL_ON_WARNING
env variable.#33404
#33299
Beta Was this translation helpful? Give feedback.
All reactions