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

Incompatible with standard 10 #16

Closed
ghost opened this issue Apr 4, 2017 · 4 comments
Closed

Incompatible with standard 10 #16

ghost opened this issue Apr 4, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented Apr 4, 2017

demonstration repo

To reproduce add standard@beta and snazzy to a project. Afterward running standard (standalone or via snazzy) will cause the error Definition for rule 'standard/no-callback-literal' was not found. Uninstalling snazzy or installing standard 9 fixes the issue.

@feross
Copy link
Member

feross commented Apr 4, 2017

Snazzy includes a copy of standard 9.x and it sounds like somehow when you run standard an older version of eslint-plugin-standard is being used with a newer version of eslint-config-standard and so the 'standard/no-callback-literal' rule that is referenced is not available in the plugin.

When I run rm -rf node_modules && npm install && npm run lint it works for me. This may be a yarn issue. Do you see the same thing?

Also, once standard 10.0.0 is released (today), this issue will go away since the versions will be in sync again. So that's at least some consolation. :)

@ghost
Copy link
Author

ghost commented Apr 4, 2017

I'm sorry for the noise. You are right that it is a yarn issue.

@ghost ghost closed this as completed Apr 4, 2017
@feross
Copy link
Member

feross commented Apr 4, 2017

No problem!

@timothystewart6
Copy link

This is the top result when searching this error so I am posting this here in case someone else finds it. If you have inconsistent versions of standard (9.x/10.x) (which is the case if you are using webpack 1.x with standard-loader 5.x and standard 10.x as your linter) you will also get this error. Upgrading to webpack 2 is going to be the solution for me.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants