addyosmani/oust

Verify latest builds can be installed

Closed this issue · 5 comments

addyosmani commented

@jackfranklin I've had a few users get in touch about not being able to install the latest version 0.0.2 with it failing on CLI permission issues (with and without sudo in use).

If you have time, could you help verify if you're able to install oust globally and use the CLI without issues? Would love to get out a patch release if needed. Thanks!

jackfranklin commented

Very odd. I get this problem too:

> npm install -g oust
npm ERR! Error: ENOENT, chmod '/Users/jackfranklin/.nvm/v0.10.29/lib/node_modules/oust/bin/oust.js'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Darwin 13.2.0
npm ERR! command "node" "/Users/jackfranklin/.nvm/v0.10.29/bin/npm" "install" "-g" "oust"
npm ERR! cwd /Users/jackfranklin
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.16
npm ERR! path /Users/jackfranklin/.nvm/v0.10.29/lib/node_modules/oust/bin/oust.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/jackfranklin/npm-debug.log
npm ERR! not ok code 0

Could this be incorrect permissions on the bin/ file? Or could it be nvm related?

jackfranklin commented

Weirdly, npm install -g oust@0.0.1 works fine.

Trying to figure what might have changed between 0.0.1 and 0.0.2 to suddenly cause this...

EDIT

Only thing I can spot is that the files setting in the package.json doesn't include the executable, but I don't think that is the problem? Plus, it was like that for 0.0.1 anyway.

EDIT 2

Eurgh, but 0.0.1 didn't have a CLI file. duh. Still trying to figure what's going on here.

@addyosmani - Pondering if it is the files option not including the bin dir. That would explain the ENOENT error?

addyosmani commented

It may be. That said, I imagine if that was the case, including the bin directory locally and install/linking would fix the issue. I think.

jackfranklin commented

It would explain why if I npm link, it works, but an npm install does not.

addyosmani commented

Hmm. I just tried a fresh release of the follow-up PR on a new machine and it looks like we're still broken. Booo.