use utils-merge instead of lodash.defaults

[andrewrk]

Hi, another packaging request here. Sorry I keep doing this to you. Here's the deal:

zip-stream depends on lodash.defaults which means to create a Debian package for zip-stream, I have to package up all of these things:

│  │  ├─ lodash.defaults (~2.4.1)                 None
│  │  │  ├─ lodash.keys (~2.4.1)                  None
│  │  │  │  ├─ lodash.isobject (~2.4.1)           None
│  │  │  │  │  └─ lodash._objecttypes (~2.4.1)    None
│  │  │  │  ├─ lodash._shimkeys (~2.4.1)          None
│  │  │  │  │  └─ lodash._objecttypes (~2.4.1)    None
│  │  │  │  └─ lodash._isnative (~2.4.1)          None
│  │  │  └─ lodash._objecttypes (~2.4.1)          None

I looked into it, and if you used utils-merge instead, it would work the same way, and utils-merge is already packaged up for Debian, so it would require no work on my part.

What do you think?

[ctalkington]

im trying to understand this "packaged for debian" stuff. can you elaborate?

[andrewrk]

Sure. I have to manually create a package for each and every dependency and then (the hard part) I have to get them approved and uploaded by a Debian developer. So when there are 8 dependencies (with only a tiny bit of code in each one) that makes it rather difficult, especially when there is already another package which does the job.

Another argument is that your README says "Dependencies are kept to a minimum..." so this pull request helps make that claim more true.

[ctalkington]

thats regarding using node built-ins. theres no built in extend. that said i could switch to node-lodash vs the deep dep trees some of the individuals have.

[andrewrk]

That would be an equally amicable solution to me.

[andrewrk]

Thanks!