So many configuration files! Why not move more of this to package.json?

Moving all possible configs to package.json can make it really packed, so that quickly navigating to a specific config becomes difficult.

When split out into their own file, many tools provide the option of exporting a config from JS. I do this wherever possible, because dynamic configurations are simply more powerful, able to respond to environment variables and much more.