-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Add more imports
eslint rules
#2589
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2589 +/- ##
=========================================
Coverage ? 32.68%
=========================================
Files ? 397
Lines ? 8835
Branches ? 954
=========================================
Hits ? 2888
Misses ? 5268
Partials ? 679
Continue to review full report at Codecov.
|
@@ -17,6 +17,7 @@ module.exports = { | |||
}, | |||
settings: { | |||
'import/core-modules': ['enzyme'], | |||
'import/ignore': ['node_modules\\/(?!@storybook)'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the usecase? I've tried to lint with this setting and without - nothing happened.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Issue: we don't get eslint errors for wrong named and default imports, which sometimes leads to bugs (e.g. #2576)
For those rules to work when importing our own packages, I had to add
jsnext:main
for all the packages that have a compiled file as theirmain