Developers duplicate shared configuration across repos and machines
Developers and teams often need the same settings in several repositories, subdirectories, or machines, but many tools do not support inheriting and merging shared configuration. They resort to copy-paste, symlinks, wrappers, or individually reviewed updates, which creates drift and can make local overrides or private paths awkward to manage. The evidence also includes broader monorepo problems—such as dependency and build tooling issues—that a configuration-sharing product would not solve.
For development teams and developers maintaining multiple repositories. Mentioned from Sep 2016 to Jul 2026 on GitHub and Hacker News.
26 different people described this problem in 21 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.1/10
- Frequency
- 10.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 4.7/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Currently the only workarounds are symlinks (which break repo-level overrides) or duplicating config in every repo
Every repository contains the exact same .vscode directory which is essentially copy&pasted all over the place. Maintaining the .vscode settings for the projects is "not pretty" compared to the tsconfig.json and tslint.json which only require the settings package to be updated with for example yarn upgrade
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 26 more quotes from people who have this problem
- Current workarounds, existing solutions and risks