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

Rule 'no-empty-label' was removed and replaced by: no-labels #410

Closed
kilianc opened this issue Feb 6, 2016 · 9 comments

Comments

@kilianc
Copy link

commented Feb 6, 2016

I am getting a bunch of errors out of nowhere after updating to latest standard!

@feross

This comment has been minimized.

Copy link
Member

commented Feb 7, 2016

Can you provide more detail about the error you're getting? What version of standard?

Rule no-empty-label was removed in standard v6 because it was deprecated by eslint, so I think you must have something really funny going on with your setup.

@kilianc

This comment has been minimized.

Copy link
Author

commented Feb 7, 2016

you must have something really funny going on with your setup.

I am sure I am, I am using babel-eslint, maybe that's the reason

@kilianc

This comment has been minimized.

Copy link
Author

commented Feb 7, 2016

removed my node_modules and reinstalled, all worked.

@kilianc kilianc closed this Feb 7, 2016

@feross

This comment has been minimized.

Copy link
Member

commented Feb 7, 2016

Nice!
On Sun, Feb 7, 2016 at 02:30 Kilian Ciuffolo notifications@github.com
wrote:

Closed #410 #410.


Reply to this email directly or view it on GitHub
#410 (comment).

@rafaeleyng

This comment has been minimized.

Copy link

commented Mar 2, 2016

I had the same error. After reading @kilianc solution, I've tried it and didn't work. Still looking for a solution.

@feross

This comment has been minimized.

Copy link
Member

commented Mar 16, 2016

@rafaeleyng This means you're using an old version of eslint-config-standard somehow. If you open a new issue and paste the output of npm ls --depth=50 I can help you.

@rafaeleyng

This comment has been minimized.

Copy link

commented Mar 16, 2016

@feross Thanks for the reply. I honestly don't remember what I did to solve that issue, but is not bothering me anymore.

@RyanCCollins

This comment has been minimized.

Copy link

commented Aug 14, 2016

@feross I have this same issue. Here is the print out from npm ls --depth=50 Thanks so much in advance if you have a fix for this 👍

<snip>
@feross

This comment has been minimized.

Copy link
Member

commented Aug 18, 2016

@RyanCCollins You don't have standard installed locally, according to that npm ls output.

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