-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow configuration file to be extended #425
Comments
This seems like a good feature request 👍 |
Do you need some help ? |
@bcoe i did look to the c8 and yargs code. In fact, we can already extends configuration if the path to the extendable config is a This is already working : {
"extends": "../../config/c8/c8.config.json",
// ...
} What about making c8 compatible with yml and js configuration ? cosmiconfig sounds good for this. Additionally, we should update the documentation. I did a branch but cannot push to this repository :/ |
Closing in favour of: With regards to cosmicconfig, I would prefer not to pull in a dependency for config management, if it can be avoided. I think it's not worth the complexity it would add to the library.
You will need to create a pull request form a fork, here's some documentation on how to do so 👍 |
I,
It would be great to be able to
extends
a configuration file to another, likeTSConfig
orEslint
do, or at least to be able to write.cjs
/.js
configuration file to require anotherjs
file.We use c8 in a mono-repo, and we cannot share a c8 configuration file between workspace:/
Thanks
The text was updated successfully, but these errors were encountered: