2 ms·
Ehh, this is just moving the mess from one location to another. All these config files can be grouped into two or three conceptual things: * Dependencies - Th
by Izkata 6y ago
Ehh, this is just moving the mess from one location to another. All these config files can be grouped into two or three conceptual things:
* Dependencies - Things required for your code to run, for example Dockerfile, package.json, yarn.lock
* Metrics - Measuring code quality, but the project works without these, such as jest.config.js, .eslintrc, .eslintignore
* Other - I don't recognize several config files here, and suspect some don't fall into the categories above, but am not sure. Also, README.md and .gitignore would fall into this category, but probably ought to remain at the top.
So instead of a generic "configs/" directory, if I was to organize these myself, I'd probably want at least two subdirectories so it would, y'know, actually be a bit more organized.