Add option to explicitly tell xo to use a config file
In my current project, my xo config file isn't in any of the parent directories of the linted files, but instead in a separate directory. However, I still want to be able to use my custom config, without having to move it to one of the parent directories or publish it to npm.
In my opinion, a decent solution to the issue would be to add a --config option to xo, which (when specified) would tell xo to use the configuration at the given path (e.g. xo --config ../.xo-config.json).
I'd appreciate your feedback, and if you agree this should be a part of xo, let me know and I'll be happy to implement this.
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too