Currently eslint is fragmented between individual packages. It probably supports monorepos & could be done at the top level, similar to prettier, with default rules that are overridden by individual packages. This reduces the maintenance burden of constantly fiddling with eslint rules in individual packages.
It also does not have a CI job currently, which it should, and this would probably be easier to do at the top level of the monorepo.
Suggest A Solution
No response
What are you currently working on that this is blocking?
Issue to be solved
Currently eslint is fragmented between individual packages. It probably supports monorepos & could be done at the top level, similar to prettier, with default rules that are overridden by individual packages. This reduces the maintenance burden of constantly fiddling with eslint rules in individual packages.
It also does not have a CI job currently, which it should, and this would probably be easier to do at the top level of the monorepo.
Suggest A Solution
No response
What are you currently working on that this is blocking?
No response