Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

~/tmp should not be the only option for build dir #3353

Closed
frioux opened this issue Apr 16, 2013 · 3 comments
Closed

~/tmp should not be the only option for build dir #3353

frioux opened this issue Apr 16, 2013 · 3 comments

Comments

@frioux
Copy link

frioux commented Apr 16, 2013

To be clear, I don't have a ~/tmp (prefer to use /tmp) and I got this error:

  npm http GET https://registry.npmjs.org/jshint
  npm http 200 https://registry.npmjs.org/jshint
  npm ERR! Error: ENOTDIR, mkdir '/home/frew/tmp/npm-11560/1366146444469-0.5005671142134815'
  npm ERR! If you need help, you may report this log at:
  npm ERR!     <http://github.com/isaacs/npm/issues>
  npm ERR! or email it to:
  npm ERR!     <npm-@googlegroups.com>

  npm ERR! System Linux 3.5.0-25-generic
  npm ERR! command "/home/frew/node/bin/node" "/home/frew/node/bin/npm" "install" "-g" "jshint"
  npm ERR! cwd /home/frew
  npm ERR! node -v v0.10.4
  npm ERR! npm -v 1.2.18
  npm ERR! path /home/frew/tmp/npm-11560/1366146444469-0.5005671142134815
  npm ERR! code ENOTDIR
  npm ERR! errno 27
  npm ERR!
  npm ERR! Additional logging details can be found in:
  npm ERR!     /home/frew/npm-debug.log
  npm ERR! not ok code 0
@luk-
Copy link
Contributor

luk- commented Apr 16, 2013

This is a duplicate of #2936. Run npm help config for further documentation.

@luk- luk- closed this as completed Apr 16, 2013
@frioux
Copy link
Author

frioux commented Apr 16, 2013

Oh sorry, I searched for tmp and thought I'd find it but I failed clearly.

@luk-
Copy link
Contributor

luk- commented Apr 16, 2013

no worries! 🌴

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants