Presets

[kevinSuttle]

So, instead of having a separate .eslintrc file, there are defined presets that can be leveraged via custom configuration objects in package.json, [like Gemfile, requirements.txt, etc., but for JS].

Example from airbnb: https://github.com/airbnb/javascript/tree/master/packages/eslint-config-airbnb

package.json

eslintConfig
{
   "extends": "airbnb/base"
}

[jonathansamines]

I also agree with this approach, actually what we need it´s the "sharable" .editorconfig configurations and a way to use this sharable configs as a extension point for another .editorconfig file. That feature will make easier to an org to share this configuration between teams/projects without have to copy/paste this files across projects.

[kevinSuttle]

http://eslint.org/docs/developer-guide/shareable-configs

[kevinSuttle]

What do you think, @sindresorhus?

[sindresorhus]

I like the idea in theory, but you need to define your request more clearly. Just linking to how ESLint does it is not enough. EditorConfig is a different. It's not just for JS. Present a better picture of how it will work. Like, how would it get the .editorconfig file to extend from.

// @vdemedes

[jednano]

Closing due to no recent activity.