Idea: auto-create .eslintrc

[silverwind]

In-Editor linter plugins like SublimeLinter-contrib-eslint_d require a .eslintrc to be present in the project directory to work. Would it be possible for xo to create one, maybe through a postinstall npm script?

[sindresorhus]

Anything stopping you from using https://github.com/sindresorhus/atom-linter-xo?

[silverwind]

Yes, primarily the fact that it's on Atom (not sold on its performance yet). Also, eslint_d is a big improvment in linting performance for big files, but I guess there might be a Atom plugin around for it.

[sindresorhus]

Sorry, I meant https://github.com/sindresorhus/SublimeLinter-contrib-xo.

[silverwind]

Oh, I wasn't aware of its existance, thanks! If you're not using eslint_d in there yet, you should have a look ;)

[sindresorhus]

SublimeLinter-contrib-xo feels fast to me. I use it continuously. Could probably be a tiny bit faster, but I don't think it's worth the complexity and fragileness it adds.

[silverwind]

Gave it a try. It works on project using xo's rules, but it also started linting my non-xo projects for some reason. Could it be that plugin doesn't actually check package.json if xo is enabled?

[sindresorhus]

@silverwind Yes, I hadn't really considered that until today. Just added it to the Atom plugin. Should add it to the Sublime plugin too. Opened an issue: xojs/SublimeLinter-contrib-xo#2

[silverwind]

Awesome, thanks!

[abhisekp]

@sindresorhus And what about webstorm? 😢

[sindresorhus]

@abhisekp #67

[teehemkay]

re: WebStorm.

I think adding a command to XO to emit a .eslintrc* config would greatly improve XO's WebStorm integration story.

Why? Because currently WS can only use ESLint directly. So using XO with WebStorm essentially boils down to having to manually configure ESLint to run like XO. Which in turns means installing various modules, eslint plugins and configs, and creating an appropriate .eslintrc* config.

(#67 doesn't do much to automate that integration with WS: it simply provide an outline of all the steps involved in setting up ESLint to work with WebStorm)

The command would work sort of like the eject option in the create-react-app tool.

It seems to me that most of the work to generate the eslint config is already done in option-manager.js. And installing XO properly installs everything that's needed by an external ˋeslintˋ (caveat: this probably implies ˋnpmˋ 3+)

With such an ˋejectˋ command available, I think that integrating XO with WS would as simple as:

$ npm install --save-dev xo eslint
$ xo --init --eject ...

The ejected config would not be used by XO only by the external eslint