Bump npm dependencies (npm test passed!)

[PeterDaveHello]

No description provided.

[thlorenz]

Please use ~ ranges, otherwise I can't accept this.

[PeterDaveHello]

@thlorenz is there any concern about using ^? Thanks.

[thlorenz]

Yes, opens up to more breakage as people don't perfectly follow semver. I prefer to be more conservative and therefore would like to stick to ~.
If you don't agree, fine, but I won't merge this since I don't wanna deal with lots of breakage issues in the future.

Thanks.

[PeterDaveHello]

So do we need to change the other dependencies also to use ~? Thanks.

[thlorenz]

Ideally yes, wasn't aware that some of them had a ^ at this point.
Most likely got introduced with another PR and I missed it :)

[PeterDaveHello]

I add a commit to use ~ in all the dependencies now

[thlorenz]

Sorry about the confusion, but of course my own repos can have ^ since I follow semver.

Also please verify that underscore's version makes sense. >= basically means we were on the latest, so we should stay on the latest.

Thanks a lot for your patience and again sorry for the confusion.

[thlorenz]

what's the latest underscore? We need to make sure we don't downgrade the version here.
Should be ~<whatever latest version is>.

[thlorenz]

My repo, so we can use ^ here (I trust myself to follow semver ;) )

[thlorenz]

My repo, so we can use ^ here (I trust myself to follow semver ;) )

[PeterDaveHello]

updated

[thlorenz]

Awesome, many thanks :)
Please squash into one commit first and then merge to master.

I made you collaborator.
So when you merge please follow this guide.
I will then version and publish to npm.

Thanks.

[PeterDaveHello]

Hi @thlorenz, IMO, these two commits are doing different their own task, one for version bump and one for syntax, can we just leave them be separated? Thanks.

[thlorenz]

@PeterDaveHello yeah, makes sense. Sounds good to me, go ahead and merge then.

[PeterDaveHello]

@thlorenz I'm confused about how should I merge it since the reference doc says not to use the green button, this PR branch is up to date, so can I merge it right here? Thanks.

[thlorenz]

Merge using git on the terminal, i.e. you'd do:

git rebase master
git co master
git merge dependencies-upgrade

It's guaranteed to be fast forward merge since you are rebasing first and if you have any conflicts you get to fix them right there.
I'm mentioning alternative ways to fast forward merges, including some links to more details here

[thlorenz]

You could also just hit the Rebase and merge option in the button dropdown, but learning to do this on the terminal is a good thing to do in general.

[PeterDaveHello]

@thlorenz Actually I totally have no problem on how to merging locally, just want to make sure the policy and procedure, if I merge it locally, will this PR also shown as "Merged"? Or it or just be closed? Thanks.

[thlorenz]

Thanks went out as 1.3 .. I did a minor upgrade since we changed a gzillion deps.