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 
You sure you want to force the 'older' node's to act like newer? May cause
a lot of hashes to update for users.

Drew Wilson
http://geedew.com
217.953.4306


On Mon, Aug 18, 2014 at 12:43 PM, Sindre Sorhus <notifications@github.com>
wrote:

> In README.md:
>
> > @@ -61,6 +61,13 @@ Default: `8`
> >
> >  The number of characters of the file hash to prefix the file name with.
> >
> > +#### options.sanitize
> > +
> > +Type: `boolean`
> > +Default: `false`
> > +
> > +NodeJS prior to v0.10.29 has a bug in UTF8 conversion from non-UTF sources like binary. The hash output will change depending on the version of Node. You can force filerev to treat UTF conversion the same as NodeJS >v0.10.28 to retain the same hashing scheme accross node versions. This will only run when true if the current version of node is less than 0.10.29 and UTF8 is the selected encoding.
> > +
>
> don't want an option for this. just do it automatically.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/yeoman/grunt-filerev/pull/40/files#r16369312>.
>