1.1.0 Broken in npm registry it seems

[steida]

No description provided.

[grabbou]

checksum invalid, so looks like the package might be broken?

[astorije]

Argh, again? I am investigating to see what's going on...

[astorije]

I reported an issue on npm (npm/npm#8822) so stay tuned. Thanks for the report @steida and @grabbou!

[grabbou]

Awesome! I hope we won't need to add post-publish tests anytime in the future :D

[astorije]

I'm not sure what to do here, and if it's a one-time error or if anytime I'll publish through Travis CI the bug will happen.
I'll leave another day or so to the npm team to look into it, but after that I'll try to manually release a version 1.1.1 as I understand it's a pain for you guys. Sorry about that!

[astorije]

And now we have travis-ci/travis-ci#4197, perfect...

[astorije]

Nevermind, I manually published version 1.1.1 and made sure this one works. So things should be solved

I'll leave this issue open until I know what happened on version 1.1.0 and until I unpublish it. I'll leave it published in case it's useful to the npm guys.

[grabbou]

I think it's already explained and can be closed. Issue was with Node version.

[astorije]

Indeed, as explained by @iarna.

Unless this gets fixed on the Travis CI end, I might have to remove node 0.11 from the .travis.yml file before the next release...