The low hanging fruit for increasing code quality is to use linter (like https://eslint.org) in every application.
That gives us ability to:
- discover problems in code from static analysis
- keep the same standards in code
- having the same code formatting in every app
It can be also configured in a way that it will automatically run as pre-commit hook so it will force developers to keep the standards and it does not allow commit code which is not compliant.
We can start with most critical checks first and then include better standards as we go, e.g. we can start with eslint to check major problems (i.e. used but not defined variables), but not checking minor problems (i.e. unused variables).
Also, code formatting can be enabled later.
The low hanging fruit for increasing code quality is to use linter (like https://eslint.org) in every application.
That gives us ability to:
It can be also configured in a way that it will automatically run as pre-commit hook so it will force developers to keep the standards and it does not allow commit code which is not compliant.
We can start with most critical checks first and then include better standards as we go, e.g. we can start with eslint to check major problems (i.e. used but not defined variables), but not checking minor problems (i.e. unused variables).
Also, code formatting can be enabled later.