Skip to content
This repository was archived by the owner on Dec 15, 2018. It is now read-only.

Conversation

@tptee
Copy link
Contributor

@tptee tptee commented Aug 9, 2016

Apparently array spread requires the Symbol polyfill:
https://babeljs.io/docs/usage/caveats/

We don't want that!

@divmain
Copy link
Contributor

divmain commented Aug 9, 2016

What's the reasoning behind removing lodash methods?

@tptee
Copy link
Contributor Author

tptee commented Aug 9, 2016

It added about 10k to the bundle (_baseiteratee being the culprit) :(

@coveralls
Copy link

coveralls commented Aug 9, 2016

Coverage Status

Coverage increased (+0.1%) to 98.374% when pulling 52fdde8 on chore/no-lodash-no-polyfills into 72b08ca on master.

@divmain
Copy link
Contributor

divmain commented Aug 9, 2016

Wow! Alright, I guess that's as good a reason as any. Anyway, LGTM.

@baer
Copy link
Contributor

baer commented Aug 9, 2016

@divmain Sooooo much lodash

screen shot 2016-08-08 at 3 39 07 pm

@tptee LGTM!

@tptee tptee merged commit 6e15ecf into master Aug 9, 2016
@tptee tptee deleted the chore/no-lodash-no-polyfills branch August 9, 2016 20:08
@ryan-roemer
Copy link
Member

@tptee @baer -- Did you try the lodash-webpack-plugin + normal lodash to get honed lodash methods?

@ryan-roemer
Copy link
Member

but, as a side note if you're pulling in lodash bespoke packages for one-each uses, it is probably the right choice to completely remove them...

@tptee
Copy link
Contributor Author

tptee commented Aug 10, 2016

Yeah, it was just single-function packages for assign and findassign was easy to remove, while find is replaced with an ugly but usable for...in.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants