Bump lodash to v4

[samhashemi]

No description provided.

[coveralls]

Coverage remained the same at 97.739% when pulling f87e51b on samhashemi:bump-deps into 987cfbe on AmpersandJS:master.

[samhashemi]

@wraithgar @latentflip @cdaringe @pgilad

I've taken a first swing at updating AmpersandJS to lodash v4. Model, View, and Events were updated to v4 in previous pull requests, so I've made 10 additional PRs to update the rest of the project.

A few of the packages depend on other ampersand packages that need to be updated, which I've noted below.

#241
AmpersandJS/ampersand-app#8
AmpersandJS/ampersand-router#52
AmpersandJS/ampersand-class-extend#9
AmpersandJS/ampersand-sync#76
AmpersandJS/ampersand-collection-lodash-mixin#11

Depends on ampersand-sync, updated above:
AmpersandJS/ampersand-collection-rest-mixin#41

Depends on ampersand-class-extend, updated above:
AmpersandJS/ampersand-collection#80
AmpersandJS/ampersand-collection-view#44
AmpersandJS/ampersand-filtered-subcollection#31

If there's anything I can do to help merge these quickly, let me know. They should all be fairly straightforward.

[pgilad]

Verified that all zuul tests run via #242

[samhashemi]

@pgilad thanks for looking through these. is there another person on the ampersand team who can give a second thumbs up?

[pgilad]

ping @AmpersandJS/core-team

[cdaringe]

+1

[lukekarrys]

+1

[samhashemi]

@cdaringe @lukekarrys thanks. could one of you look through the related commits above? these changes are much more impactful if they are done across the ampersand project -- it makes it possible to transition entirely to lodash v4 instead of requiring two different versions. This can be a huge difference in number of bytes.

[samhashemi]

@cdaringe @lukekarrys @pgilad i'm getting the sinking feeling this project isn't being actively maintained.

is there a clear person i should work with to get these merged and pushed to NPM? is the best option forking all the libraries?

[cdaringe]

hey @samhashemi, sorry to give that impression :/ my experience has told me that we've had the implicit practice of letting the package maintainer take charge of merge/publish. im not sure who does -state, but i'm sure it was just a case of "too-busy." thanks for following up. we'll get it taken care of.

[cdaringe]

@pgilad let me know if you want me to publish

[samhashemi]

@cdaringe thanks! is there a list of who the maintainer is for each ampersand project? i'd like to get the 10 PRs above merged in parallel.

[latentflip]

@cdaringe I think at one point I was, but I'm taking a back seat from things right now, so if you have publish bits go ahead and do what you think's right :)

[cdaringe]

@samhashemi, it should be listed on the packages (like here)
@latentflip i'll add ya as such ^^ for this package (even in presence of the backseat comment for now, just to remove ambiguity). if we need to swap out or elect a new lead for this pkg, let's get a new thread goin!

i'll publish this bad boy :)

[cdaringe]

5.0.2 is up!

[latentflip]

Okay, I definitely shouldn't be listed as I'll be of no use, so I opened this: #243

[pgilad]

Publish, and publish all related repositories as well... I didn't have publish rights to all of them so decided not to get stuck in the middle of the upgrade. I do admit I use ampersand less these days (react + redux mainly) but am happy to contribute when I have time