4 ms·
Their main motivation seems to be CI, where people often lint the entire repo on every PR.
by sapiogram 3y ago
Their main motivation seems to be CI, where people often lint the entire repo on every PR.
- msoad 3y agowhich is a really weird problem to have. Only lint files that have changed? How hard that is? our monorepo is 3m lines of code and running lint is not a bottleneck by any means... And once in a while that we have to run lint for entire repo (ESLint upgrade for example) we can afford to wait 1 hour ONCE
- Aeolos 3y ago50-100x faster would turn that 1 hour into 1 minute. It's not that you can't wait 1 hour, it's that you don't have to wait. Think of all the wasted cycles that could be put to better use...
- ForkMeOnTinder 3y ago> Only lint files that have changed? How hard that is? Quite hard, especially since type-aware rules from e.g. https://typescript-eslint.io/ https://typescript-eslint.io/ mean that changing the type of a variable in file A can break your code in file B, even if file B hasn't changed.
- msoad 3y agoWell, this solution won't help with those rules since your bottleneck is now tsc.
- mrkeen 3y ago> we can afford to wait 1 hour ONCE If you lint the entire repo, fix every issue in one try on the first go, and then lint the entire repo to double-check, that's two hours. But my workflow is usually: lint the repo -> fix one thing -> repeat