Super helpful tool. Thanks for building and sharing it with the world.
I had this addition in my mind where genie could also help in decluttering the config file mess we have in modern projects.
I thought about an approach where a .genie directory could live in the root of the repository and contain the config files that genie uses to render the files into the respective packages. genie could follow a similar approach to what stow does.
Example:
.genie/
packages/
pkg-a/
package.json.genie.ts
.eslintrc.js.genie.ts
pkg-b/
biome.json.genie.ts
This would lead to files being rendered into:
packages/
pkg-a/
package.json
.eslintrc.js
pkg-b/
biome.json
This could really declutter the overall codebase when combined with the VS Code settings (settings.json) for excluding files:
"files.exclude": {
"**/.*": true,
"**/biome.json",
"**/package.json"
}
Super helpful tool. Thanks for building and sharing it with the world.
I had this addition in my mind where
geniecould also help in decluttering the config file mess we have in modern projects.I thought about an approach where a
.geniedirectory could live in the root of the repository and contain the config files thatgenieuses to render the files into the respective packages.geniecould follow a similar approach to what stow does.Example:
This would lead to files being rendered into:
This could really declutter the overall codebase when combined with the VS Code settings (
settings.json) for excluding files: