-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
ESLint: Issues highlighted in default airbnb styleguide valid? #463
Comments
You're welcome to add PRs fixing this. TBH, I haven't gone through the list of changes in a while so I'm not entirely sure why some of the exceptions were made originally. It's on my mental list of TODOs for the 1.0 release but isn't something I'm going to get to soon and perhaps not for the 0.x line. |
Ok cool, I'll see what low-hanging errors I can find and fix, if there isn't an underlying reason for it. I think the unresolved gatsby-helpers module can't be solved as it's not on NPM & imports not being resolved due to missing extensions might be tricky due to webpack? Will look into it. |
That particular problem will be fixed in 1.0 as we'll be moving Gatsby to a Lerna monorepo so gatsby-helpers will be published separately to Github. |
I was initially annoyed when I got the Then I figured out that you can configure ESLint to consider certain packages as 'core' to get rid of this warning. My
Core modules docs: https://github.com/benmosher/eslint-plugin-import#importcore-modules |
I'm not sure whether it's appropriate, but I think that |
@KyleAMathews Why did you close this? I think that using |
@KyleAMathews Fantastic! I'm amused by your quick and accurate responses, keep up the great work! |
Some of the React best practice warnings and import warnings highlight reasonable issues in the code; is there a reason these aren't being followed? Especially regarding the module imports; as having a resolvable/valid package.json file could help in portability between gatsby and a plain npm react project.
The text was updated successfully, but these errors were encountered: