Fix lint:fix package script
Explanation
Some developers run yarn lint:fix before pushing. After the ESLint 9 upgrade, however, this package script has been broken because it fixes all lint warnings in addition to errors. Since there are many, many warnings, this ends up making all kind of changes.
This commit gets this script in working order again by passing --quiet to the ESLint script, which, when given in combination with --fix, instructs ESLint to exclude warnings from being autofixed.
References
Manual testing steps
- Run
rm .eslintcacheto clear the ESLint cache. - Run
yarn lint:fix. - No files should be changed (because there are no lint errors on
main).
Checklist
- [x] I've updated the test suite for new or updated code as appropriate
- [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
- [x] I've highlighted breaking changes using the "BREAKING" category above as appropriate
- [x] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes
I'll have to think about this again. It seems odd that yarn lint would list warnings but yarn lint:fix would not. I think we should continue to list warnings but just autofix the errors. I'll probably have to implement something custom to do that.