DEV Community

Cover image for Keep your JavaScript repository clean
Dragoș Străinu
Dragoș Străinu

Posted on • Originally published at

Keep your JavaScript repository clean

As your JavaScript project grows, you start adding more tools and settings that will improve the development experience.

Nowadays, tools like eslint, husky, and tests are essential for any project.

The problem is that most of these tools require a config file at the root of your project/repo.
After some time, the root directory is full of config files, and it's a bit intimidating when you open it in the git hub.

One elegant solution I found in remirror repo.
There all config files that should stay in the root of the project are actually in the ./support/root/ directory,
and they are locally symlinked when setting up the project.

Inspired by their approach I created symlink-config, which helps to migrate your project to this approach.

Here is how repo looks on Github before and after:

Default With symlink-config
root config files demo root symlink config files demo

This demo has only 5 configs in the root, but imagine adding more tools, like tsconfig.json, jest.config.js, and others.

When exploring the project locally,
all these files will be in the root but being just a symlink file they will differ from the rest of the files and you may skip them visually.

In the end, I think this tool is useful for big open source projects with a lot of config files, as it cleans up the entry point of the project (the repo root) and makes it more appealing to users.

Check out symlink-config, and let me know your opinion!

Top comments (1)

iamandrewluca profile image
Andrei Luca • Edited

Great idea!
Taking into consideration that most of the libraries use cosmiconfig, this problem would be nice to be solved directly in the library