You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could this be built as a separate CLI tool on top of standard-engine? A lack of configuration/options/deviation was one of the original goals of standard, and allowing everything to be overridden by a local .eslintrc may undermine that goal.
It could also get confusing if someone has an old .eslintrc file in their project and things start acting strange (I guess this would be the "breaking" part).
I do like this idea though! We could add it as a configurable option to standard-engine but I don't know how keen @feross and others would be on adding it to standard.
Is this a simple matter of allowing the user to set the useEslintrc eslint option? If that's all it is, I don't see the harm in letting users of standard-engine set it.
That said, it was an explicit decision to not do this for standard itself, as this would make standard behave differently on different machines, if a user keeps their code in ~/code and a config file in ~/.eslintrc, which actually bit me once.
I think the solution that standard will offer for this is to just allow rule overrides directly in package.json for those who just need to change a rule or two for their project. But that's separate from this issue.
standard/standard#351 (comment)
It'd be nice for standard-engine to pick up your local
.eslintrc
. You can set your eslintrc to this, and customize it as you see fit.Rationale:
As a bonus, maybe it can be defined in package.json as an alternative (much like babel lets you define options in
.babelrc
andpackage.json
/babel
)The text was updated successfully, but these errors were encountered: