CodeClimate

[knownasilya]

How do we get CodeClimate to honor standard and not trigger issues that really don't exist?

Seems like there is a codeclimate config, but it's not exactly clear how to make it work. Do I really have to use eslint-standard?

Related issue on my project: Strider-CD/core#14 You can see my setup there.

[knownasilya]

Looks like eslint modules aren't supported by codeclimate.. codeclimate/codeclimate#79

[feross]

Looks like this issue might be caused by CodeClimate not supporting a custom JS parser, like babel instead of the default that's built into ESLint. standard just uses the default one, unless you specify otherwise.

This isn't an issue with standard.

[knownasilya]

I don't think it's the parser so much, as it is the "extends": "standard" syntax, which loads an eslint module, e.g. https://github.com/feross/eslint-config-standard

[feross]

Does it work if you npm install eslint-config-standard?

[mikz]

CodeClimate just added standard to their engine: codeclimate/codeclimate-eslint#75 (comment)

[knownasilya]

Yay!