Skip to content
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

feature request: use .eslintrc to simplify configure #722

Closed
septs opened this issue Dec 15, 2016 · 9 comments

Comments

@septs
Copy link

commented Dec 15, 2016

I want to detect that the .eslintrc file exists by reusing the .eslintrc configuration
This avoids repeating the .eslintrc configuration once again in package.json

@septs

This comment has been minimized.

Copy link
Author

commented Dec 15, 2016

@LinusU

This comment has been minimized.

Copy link
Member

commented Dec 15, 2016

There is no configuration of standard, that is the point of it. Or maybe I'm misunderstanding what you are trying to do?

@LinusU

This comment has been minimized.

Copy link
Member

commented Dec 16, 2016

But with standard you don't need an .eslintrc config at all, so it isn't repeating?

@feross

This comment has been minimized.

Copy link
Member

commented Dec 17, 2016

Standard doesn't recognize .eslintrc files, intentionally. This is to ensure that standard rules can't be modified unexpectedly by random .eslintrc files on your filesystem.

@feross feross closed this Dec 17, 2016

@chuyik

This comment has been minimized.

Copy link

commented Jan 12, 2017

@septs Here's the configurable standard for you:
https://github.com/o2team/standard-own

Git it a try if you like :D.

@jcrben

This comment has been minimized.

Copy link

commented Apr 9, 2017

Stuffing more things into package.json is annoying. Also the CLI tool standard doesn't seem to do much that theeslint CLI doesn't alreay do. Ideally the README would strongly discourage using standard globally, but instead it seems to encourage it: https://github.com/feross/standard#install

standard-own seems cool, but I'd rather not have an underlying dependency on a project which doesn't make it easy to customize. That runs contrary to the customizable philosophy of eslint. So I'm switching to eslint-config-airbnb.

I did see that there's another option to extend the underlying eslintrc: https://github.com/feross/standard#i-disagree-with-rule-x-can-you-change-it

@LinusU

This comment has been minimized.

Copy link
Member

commented Apr 10, 2017

You can use eslint-config-standard the same way you would use eslint-config-airbnb 👍

@feross

This comment has been minimized.

Copy link
Member

commented Apr 10, 2017

@jcrben If you want to use standard as your starting point and add/remove/change some of the rules, take a look at eslint-config-standard.

The standard cli is for users who want to use that ESLint configuration without knowing anything about ESLint and without allowing rules to be customized. For many teams, the mere option to customize the tool can lead to endless bike-shedding and wasted time, so this is a feature, not a bug.

For those who want customizability, we offer eslint-config-standard which I hope you'll take a look at! Cheers!

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
5 participants
You can’t perform that action at this time.