Closed tim-field closed 9 years ago
Its fixed in the latest commit. That first condition doesn't make much sense.
But v.0.1.1 isn't a valid install target currently.
npm ERR! argv "node" "/usr/bin/npm" "install" "shipit-npm@^0.1.1" "--save"
npm ERR! node v0.12.2
npm ERR! npm v2.8.3
npm ERR! code ETARGET
npm ERR! notarget No compatible version found: shipit-npm@'>=0.1.1 <0.2.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.0.3","0.0.4","0.0.5","0.1.0"]
Hi @timbofield looks like i forgot to publish should be all good now.
Perfect thanks!
I'm not sure what this message is getting at. I thought shipit-npm itself would call init first ?