title: What are the benefits of adding configs to package.json?
body: <p>I have always placed different "tooling configurations" in their own files in my front-end projects. </p>
  
  <p>For example: babel in <code>babel.config.js</code>, jest in <code>jest.config.js</code>, eslint in an <code>.eslintrc.json</code>, etc.</p>
  
  <p>I have noticed recently however that it is possible to place many of these configurations directly in a projects <code>package.json</code> file instead. </p>
  
  <p>I did some digging around online and asked a few colleagues but no-one can seem to give me a definitive answer as to why one might prefer one approach over the other.</p>
  
  <p>Is it purely a matter of preference?</p>