DEV Community

The state of a modern repo

Marcus Christensen on August 11, 2021

Background During the years I have seen many tools and technologies both rise and fall, both good and bad attempts on solving different ...
Collapse
 
klvenky profile image
Venkatesh KL

Definitely true with the bunch of config files during in the for of the repo.
I normally see these list

  1. Package.json
  2. Yarn.lock/package-lock.json
  3. Prettier and / or editorconfig
  4. Gitlab ci/ circle CI / GitHub workflows config etc
  5. Makefile or setup if if requires some custom config.

So they all make the barrier of entry a little higher. Probably we could create a single to level file that shares a link to all the config files which are in another sub directory. It doesn't help much but keeps the repository beginner friendly.