deathcap / nodeachrome

run Node.js scripts in Google Chrome (experimental)
MIT License
2 stars 0 forks source link

npm install with browser fails: ENOENT: no such file or directory, mkdir #26

Open deathcap opened 8 years ago

deathcap commented 8 years ago

./host/cli.js npm install ucfirst fails with an error in mkdir:

Starting...
Started pid=6, argv=["/bin/node","npm","install","ucfirst"], env={"TERM":"xterm-256color","SHELL":"/bin/sh","USER":"user","LOGNAME":"user","PATH":"~/.bin/:/usr/bin/:/bin:/usr/sbin:/sbin:/usr/local/bin","PWD":"/","HOME":"/home"}
info it worked if it ends with ok
info using npm@3.6.0
info using node@6.0.0
npm ERR! Browser 5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36
npm ERR! argv "/bin/node" "npm" "install" "ucfirst"
npm ERR! node 6.0.0
npm ERR! npm  v3.6.0
npm ERR! code [ 'Error: ENOENT',
npm ERR! code   'ENOENT',
npm ERR! code   index: 0,
npm ERR! code   input: 'Error: ENOENT: no such file or directory, mkdir \'/Users/admin/games/voxeljs/nodeachrome/sandbox/tmp/npm-6-42feffdf/registry.npmjs.org/ucfirst/-\'' ]
npm ERR! Error: ENOENT: no such file or directory, mkdir '/Users/admin/games/voxeljs/nodeachrome/sandbox/tmp/npm-6-42feffdf/registry.npmjs.org/ucfirst/-'
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

./host/cli.js npm view ucfirst works however. Could be a bug in app/userland/fs.js

deathcap commented 8 years ago

Check mkdirSync