Fixing a regression bug

When removing the ~ (tilde) syntax from `package.json`, it was not replaced with thew new ^ syntax.
Version 0.2.1 therefore was using 0.1.3 of each-async, while Version 1.0 regressed to 0.1.0 of each-async.

- Adds ^ syntax to each-async
- Sets minimum each-async to 0.1.3

*Note* Tests are failing for me. The hashes for md5 do not match what's in the test cases. This looks more like an issue with the previous hashes using crypto.createHash at a different version with (somehow?) different output. I cannot explain that.

Fixes #39 
we shouldnt have to check for the right version of node. a better thing would be to check to see what hash the file has been created with and check to make sure that matches whats in the config. Doesn't really matter what the hash is as long as its unique.