Change Details

@Sniedzielski shared with other devs in today's front-end developer group meeting the code hygiene approach to move all ESLint ignores from `package.json` into distinct `.eslintignore` file Advantages of `.eslintignore` file - .eslintignore in line with files like .gitignore - package.json doesn't become a huge collection of things Advantages of `package.json` - one place for dev tooling - reduces clutter in top directory of projects, some projects were going that way No matter which way will be selected, consistency across projects should be a prime factor. Further reading: https://eslint.org/docs/user-guide/configuring

@Sniedzielski shared with other devs in today's front-end developer group meeting the code hygiene approach to **move all ESLint ignores from `package.json` into distinct `.eslintignore` file ** Advantages of `.eslintignore` file - .eslintignore in line with files like .gitignore - package.json doesn't become a huge collection of things Advantages of `package.json` - one place for dev tooling - reduces clutter in top directory of projects, some projects were going that way No matter which way will be selected, consistency across projects should be a prime factor. Further reading: https://eslint.org/docs/user-guide/configuring Related call from T203648#4578269

@Sniedzielski shared with other devs in today's front-end developer group meeting the code hygiene approach to **move all ESLint ignores from `package.json` into distinct `.eslintignore` file ** Advantages of `.eslintignore` file - .eslintignore in line with files like .gitignore - package.json doesn't become a huge collection of things Advantages of `package.json` - one place for dev tooling - reduces clutter in top directory of projects, some projects were going that way No matter which way will be selected, consistency across projects should be a prime factor. Further reading: https://eslint.org/docs/user-guide/configuring Related call from T203648#4578269