Decoupled & Composable Infrastructure
Decouple your infrastructure with composable auto-ignored template generation Files.
- Decouple Codependent Config Files: manage codependent config files like
.vscodefiles in a separate directory or module.
- Decouple devDependencies: Create your final
package.jsonfrom composable pieces of
package.json. This allows you manage devDependencies as a separate repository.
- Compose Your Dev Environment: Compose elements of your dev environment and infrastructure from smaller pieces.
esopsuses user-defined explicit merge rules and enforces the use of git tags for immutable version management for infrastructure components.
- Provide Reference Implementations and Design Docs: Create reference implementations that can be installed without polluting your
Packs To Try
||Have typescript with node tests ready to go.|
Install globally or locally
npm install -g esopsyarn global add esops
npm install -save-dev esopsyarn add esops --dev`
Config esops in
If global, just run
esops. If local, use
npx esops. Files will be generated, and if you have a
.gitignore, it will be updated to include the generated files.
To Clean Files
There are so many developer tools out there, like
typescript, that have codependent config files that have to be available at the root level of project to enable features like code editor integration. The management of these files can be considered a separate concern from your project goal.
By separating these files, and adding them as auto-ignored template files, you can update and manage your infrastructure separately from your client code.
eslint settings? Need to support
prettier now? Someone on the team wants better
vscode integration? With
esops, generated files don't pollute git or npm, thus not having to deal with rebasing or codgen issues that happen with other template generators.
- Logo: Gilbert Baker Font