feat: make eslint emit warnings only during development
Changes
Reported by @doitadrian
While in development, errors are reported much more aggressive than what we had with Webpack 4. So aggressive that it becomes annoying very quickly.
For example, let’s say I have a div with an icon in it and I just want to remove the icon to see how the div will look like. What would happen is, in the app, I’d get an overlay that reports an ESLint error, saying that icon const is defined but never used. That wasn’t the case before.
It’s alright for these kinds of errors to be reported if the app is being built, but in development mode, warnings will suffice.
This PR turns off some TS config flags, that causes to report not used parameters & local variables as errors and make all eslint errors to be shown as warnings during development.
How Has This Been Tested?
Make some error, like create a not used variable inside admin App.tsx file and run yarn webiny watch apps/admin --env dev.
Documentation
Not needed I guess.