I have the following setup:
- different teams
- shared eslint config (that imports airbnb rules as a basis).
Whenever a developer decides to update libraries, if eslint/prettier have updates, it's a pain. The main reason is becuase normally eslint or prettier are introducing new rules. If we update these libraries, they implicate, most of the times, in reformatting the entire code. I personally don't think this is a good practice, because:
- it clutters the log.
- you're adding new rules that the teams are not aware (impacts can be huge)
- Steps 1 and 2 will always repeat whenever you update the libs.
Giving the step 3 I mentioned, it makes me wonder if it makes sense to update these libs.
When we didn't have anything, following airbnb rules was great. But does it make sense to keep including new rules and reformatting the code whenever you update a library. (for instance, we have establish a process of updating the frontend libraries once a month to avoid having deprecated libs. Not updating the eslint rules and waiting longer proved to be even worse.
I wanted to know how do you guys handle it and what are the best practices on it.
Since this is more process-related question, software engineering seems to be the right place to ask.