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

2.0.1 seems broken? #5

Closed
mrjmd opened this issue Sep 19, 2018 · 3 comments
Closed

2.0.1 seems broken? #5

mrjmd opened this issue Sep 19, 2018 · 3 comments

Comments

@mrjmd
Copy link

mrjmd commented Sep 19, 2018

Adding the gatsby-plugin-eslint to a brand new gatsby v2 project seems to fail currently. I was trying to add this to an existing project and it was failing, so I tried it out with a fresh install and had the same issue. Steps to reproduce:

  • gatsby new projectname (build new gatsby project with latest default starter, currently that's giving me gatsby 2.0.4)
  • gatsby develop (everything loads fine)
  • npm i --save-dev gatsby-plugin-eslint (currently adds v 2.0.1)
  • npm install --save-dev eslint eslint-loader
  • add the default config in gatsby-config.js to plugins - 'gatsby-plugin-eslint',
  • gatsby develop

This produces the errors in the screenshot below:

screen shot 2018-09-19 at 9 51 11 am

@mrjmd
Copy link
Author

mrjmd commented Sep 19, 2018

Possibly related: webpack-contrib/eslint-loader#209

@JustFly1984
Copy link

Please update to support eslint 5

@mongkuen
Copy link
Owner

I'll be updating to eslint 5 shortly, finally getting around to things

But this error specifically is "No ESLint configuration found" because there is no .eslintrc file found.

You can fix it by just dropping an empty .eslintrc file in the project root.

I added more details into the readme instructions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants