-
Notifications
You must be signed in to change notification settings - Fork 142
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
Refactor/depends on lodash #51
Refactor/depends on lodash #51
Conversation
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.
@tomchentw thanks! though I still prefer what you originally suggested with lodash/isString
etc.
Is there any reason you didn't use that [or am I missing something about how babel-plugin-lodash
works]?
@JaKXz that's how it looks like when running |
@tomchentw oh ok, cool. Would destructuring those methods out of |
@JaKXz I think so! Would you like switching to destructing format? |
Yes, please :) |
…ash.issymbol" from dependencies * Ref #22
@JaKXz updated! |
1 similar comment
Thanks @tomchentw! I'm going to bed now but I will release this by the end of the week when I have OSS cycles again :) In the meanwhile please feel free to install |
|
Awesome! |
Before
After
Thus, for those users who's also using
lodash
in their user space, the bundler (rollup/webpack) could resolve these modules and create a smaller output.