Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Errors on 'no-empty-label' when there is no rule with that name.

See original GitHub issue

What version of ESLint are you using? eslint v3.2.0 node v6.3.0 npm 3.10.3

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration: No config needed to show issue.

What did you do? Please include the actual source code causing the issue.

$ ./node_modules/.bin/eslint src/

What did you expect to happen?

 2:10  error  'hello' is defined but never used                                            no-unused-vars

What actually happened? Please include the actual, raw output from ESLint.

/dev/src/index.js
  2:1   error  Rule 'no-empty-label' was removed and replaced by: no-labels                 no-empty-label
  2:1   error  Rule 'space-before-keywords' was removed and replaced by: keyword-spacing    space-before-keywords
  2:1   error  Rule 'space-after-keywords' was removed and replaced by: keyword-spacing     space-after-keywords
  2:1   error  Rule 'space-return-throw-case' was removed and replaced by: keyword-spacing  space-return-throw-case
  2:10  error  'hello' is defined but never used                                            no-unused-vars

Issue Analytics

State:
Created 7 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

gyandeepscommented, Jul 31, 2016

you can use root: true inside a config file that way eslint will stop looking upwards from that config.

0reactions

riptercommented, Jul 31, 2016

Ah, that was it. I didn’t know eslint would go out of my root directory searching for a config. There was a bad .eslintrc file in my root dev folder. I removed it and everything is working as expected. Thank you!