Consider removing lodash modules

[phated]

If we can find frozen modules that are battle tested to replace them, we should probably switch.

[jonschlinkert]

@phated I have some libs that might help for some of them.

that are battle tested

I'll add some download stats for them, I'll leave it to you to decide if they make sense for bach. If you decide any of them are ok, I'll make sure they get bumped to 1.0 etc if they aren't.

• flatten: https://github.com/jonschlinkert/arr-flatten (82m dls)
• map: https://github.com/jonschlinkert/arr-map (700k dls)
• last: https://github.com/jonschlinkert/array-last (36k dls)
• filter: https://github.com/jonschlinkert/arr-filter (150k dls)
• each: https://github.com/jonschlinkert/array-each (90k dls)
• initial: https://github.com/jonschlinkert/array-initial (<500dls)

[phated]

@jonschlinkert I believe we are using map and reduce to iterate over objects or arrays

[jonschlinkert]

got it, "collections" not just arrays. I have collection-map does both objects and arrays - the underlying libs are pretty heavily used but it's light on the downloads, probably b/c of the name. I also have object.map and object.reduce, but obviously those wouldn't work since they only handle objects.

[doowb]

collection-map handles both objects or arrays.
for-own will handle both objects and arrays.

... @jonschlinkert just responded right before I hit "Comment"

[doowb]

I mentioned for-own above, but that would be a replacement for lodash.foreach which is only being used on arrays in bach. If that's the case, then array-each should be a good replacement.