3 ms·
> Not everyone wants to install ESLint in every package.json I don’t understand why? Adding the config to the repo takes minutes, and then you’re good: it’s sh
by thiht 2y ago
> Not everyone wants to install ESLint in every package.json
I don’t understand why? Adding the config to the repo takes minutes, and then you’re good: it’s shared with all the contributors and can work in CI.
Not sure why you would want to settle for "works on my machine"?
- suzzer99 2y ago1. It slows down CICD install times for every repo. 2. I'd rather not have to make the same ESLint config change to 30+ repos. 3. I'd rather not have to update ESLint plus plugins in 30+ package.json files.' We don't use ESLint as any kind of CICD gateway and we don't enforce what IDE/linter people use. It's not important to us to have perfect uniformity across every developer's machine.
- suzzer99 2y agoI just added fetch to my globals array in my global .eslintrc file and I didn't have to add it to 29 other repos. That was nice.