Better interop with ESLint?

Ok, this is hard to explain. I really like XO, but it is just a very thin wrapper around eslint nowadays, with eslint config in package.json and the various editor plugins for eslint having also discovered the fix capabilities of eslint.

Furthermore, eslint plugins have npm dependencies for eslint, but XO pulls in eslint so it is missing from the project’s package.json, leading to warnings, or else you have to manage eslint anyway.

It is really nice that XO plays the role of curator, pulling in useful eslint configs and plugins as they become available (❤️ AVA) .

So I am wondering if it would not be better if XO was only a CLI tool to run eslint and manage the eslint config and dependencies in package.json, but as far as npm and the editors are concerned, there is only eslint… I would like to run xo update-config and it would do all the things that would have happened with xo as a direct dependency, except that the rest of the eslint ecosystem understands what’s going on…

[wmertens]

I just found another use for this: codeclimate.com uses eslint as part of their analysis, and they need an eslintrc…

[sindresorhus]

Continued in #272