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

Running npm test in TravisCI #643

Closed
kuronaru opened this issue Sep 28, 2016 · 3 comments

Comments

@kuronaru
Copy link

commented Sep 28, 2016

I've been using standard for awhile and it's my first time encountering this.
I always run npm test before pushing code to GitHub and have TravisCI integration and it's my first time seeing this error:

> standard
standard: Unexpected linter output:
Error: standard:
    Configuration for rule "no-constant-condition" is invalid:
    Value "2,[object Object]" has more items than allowed.
Referenced from: /home/travis/build/kuronaru/qazi/node_modules/standard/eslintrc.json
    at validateRuleOptions (/home/travis/build/kuronaru/qazi/node_modules/eslint/lib/config/config-validator.js:102:15)
    at /home/travis/build/kuronaru/qazi/node_modules/eslint/lib/config/config-validator.js:148:13
    at Array.forEach (native)
    at Object.validate (/home/travis/build/kuronaru/qazi/node_modules/eslint/lib/config/config-validator.js:147:35)
    at load (/home/travis/build/kuronaru/qazi/node_modules/eslint/lib/config/config-file.js:390:19)
    at /home/travis/build/kuronaru/qazi/node_modules/eslint/lib/config/config-file.js:326:36
    at Array.reduceRight (native)
    at applyExtends (/home/travis/build/kuronaru/qazi/node_modules/eslint/lib/config/config-file.js:309:28)
    at Object.load (/home/travis/build/kuronaru/qazi/node_modules/eslint/lib/config/config-file.js:395:22)
    at loadConfig (/home/travis/build/kuronaru/qazi/node_modules/eslint/lib/config.js:74:33)
If you think this is a bug in `standard`, open an issue: https://github.com/feross/standard/issues
npm ERR! Test failed.  See above for more details.
The command "npm test" exited with 1.
@feross

This comment has been minimized.

Copy link
Member

commented Sep 29, 2016

In addition to standard, are you depending on an old version of eslint? You should remove any eslint dependencies.

If you can't figure it out, please paste the output of npm ls --depth=50 here.

@ghost

This comment has been minimized.

Copy link

commented Nov 10, 2016

Confirmed.
also tried with the latest eslint.
issue.standar.txt

@feross

This comment has been minimized.

Copy link
Member

commented Nov 23, 2016

Try removing gulp-eslint which is depending on an old version of eslint.

@feross feross closed this Nov 23, 2016

@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.
3 participants
You can’t perform that action at this time.