-
Notifications
You must be signed in to change notification settings - Fork 119
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
Node reducer was refactored #48
Conversation
@nailxx Wait a moment. Weird conflicts presence again :( |
…itions and sizes for all elements on patch and pass it into components
…y that binds methods and data for component (in constructor)
…asks better (though not as elegant looks)
…there is unable to resolve path to module somehow)
…e width, correct eslint and etc
ddb4173
to
3ce6919
Compare
@nailxx Done. |
It should be fixed by @brusherru I think |
@@ -22,7 +22,7 @@ module.exports = { | |||
], | |||
|
|||
'settings': { | |||
'import/resolver': ['node', 'webpack'], | |||
'import/resolver': {'node': {"extensions": [".js", ".jsx"]}, 'webpack': {}}, |
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.
Hmm.., does it work that way? What’s the difference between node & webpack in our context?
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.
I am not into these details and am not alone.
Read following discussion: import-js/eslint-plugin-import#139
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.
Thanks. So can we remove webpack
key from resolver settings completely?
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.
Yes, we can.
No description provided.