Updated packages

[kahwee]

Hey, not sure if you're okay with this. I think running tests on browserify ~v9.0.0 makes more sense since that is the most likely version people would be using in the near future.

[maxnordlund]

Don't know about the dependency change, but please change the commit message. That style is fine for pull requests, but not something that will be remembered until the end of time. Commit message styles has been discussed on Stackoverflow and it references a blog post that gives a sane default.

---

If you didn't know already, here's how to do it:
When you want to change the last commits message, just run git commit --amend and it will drop you into an editor with the current message and some help text. Once your done just run git push --force to overwrite the old commit message with the new one.

[sukima]

I found these resources very helpful:

• http://www.codeography.com/2015/02/17/great_commit_message.html
• http://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message
• http://rakeroutes.com/blog/deliberate-git/

The best take away was the because clause. Here is my guidelines (rule of thumbs) that I abide by:

• Subject line is 50 character or less
• Subject starts with a command in present tense: "Fix", "Update", "Refactor", "Move", etc. and not "Fixes" or "Fixed".
• Body is wrapped at 72 characters but don't wrap URL's.
• Body is in Markdown syntax.
• Never use git commit -m always on open in an editor. This forces you to think about the message an prevents rambling.
• When in doubt add the word "because" to the body and go from there.
• If the code change doesn't warrant a commit message that follows the above then it should probably be rebased differently.

[kahwee]

No problem, I'll take a look and update the commit messages 12 hours later. Thanks for the links.

[eugeneware]

Great resources @sukima !

[kahwee]

I updated the commit messages. Thanks all.

[sukima]

Awesome! @maxnordlund what do you think?

[maxnordlund]

It's very much better, I'm happy as it is right now. What about the actual change? Ping @sukima and @eugeneware

[sukima]

I don't know of the changes between the change in versions to the dependencies. I don't anticipate any breaking changes.

I ran the latest tests on this branch and the four tests pass. My take is the only way to be sure it is all good is to release it to the wild. So I'll merge and it can be reverted if others find problems.

[maxnordlund]

Good, that seams reasonable. Thanks, @eugeneware can you add @kahwee to the repo as per #53