grunt-hashres is a dependency of a repo I contribute to, HabitRPG. Using npm install to load it up (on my Windows 7 machine, anyway; not sure if it'd break elsewhere) throws an ENOENT error and craps out. It looks like npm attempts to create *3$3.js from the "Tests for 'Escape Special Characters' pull request", fails because * is a wildcard character not allowed in a Windows filename, then brings the npm install to a halt when it discovers that the file is missing. Any chance *3$3.js could be removed, or use different special characters for its purpose?
Thanks for letting me know. I'll fix it. In the meantime, I recommend you to specify the previous version (0.3.2) in your package.json.
Oddly, that hasn't worked. I first encountered the issue with it pointed at 0.3.2. Maybe some of the other dependencies look at v0.3.3 in their turn? (I'm not an npm expert, heh)
Ah, we were using semantic versioning--maybe it was grabbing 0.3.3 anyway. Thanks for the fix!
New version has been deployed in npm. It might not be available for a few minutes. Make sure that your package.json points to ~0.3.4 and run npm install. That should work. If not, remove the old package first: npm remove grunt-hashres and then npm install.
npm remove grunt-hashres