-
Notifications
You must be signed in to change notification settings - Fork 434
Installing [email protected] fails #279
Comments
Seeing this too after noticing some failing CI builds. |
Also fails on Jenkins on windows
|
thanks, i have unpublished v1.9.14 until we understand the problem |
does anybody have any pointers to public travis-CI builds with this error? we've been trying to replicate but we haven't been able to. |
Yeah, it'd be helpful for me to figure out the issue(s) in fs-extra as well. |
Nope, sorry. I saw this on a private Jenkins installation. The only possibly useful information I can think of is that PhantomJS was not installed globally on this machine prior to running the command. |
issue has been filed as jprichardson/node-fs-extra#108, the key step was having a machine with a temp directory on a different device than the install directory. |
Anything more needs to be done for this? I'm still seeing the issue with [email protected]:
|
I just tried this and was unable to reproduce on either OS X Yosemite or Ubuntu Linux 14.04. Which Node / npm versions are you using? |
Here's my setup: /workspace is shared via Virtualbox shared folder, so /tmp ends up on a different device (which seems to be what this bug was originally about). Let me know if you need anything else. |
I am seeing this issue on: OS X Yosemite /code is mounted via virtualbox and is Ubuntu Linux 14.04 machine
|
Hi @nicks, I'm still seeing this issue with [email protected], any sign of a resolution? I'm on Windows 7 Host Cheers!
|
We are seeing the same issue with 1.9.16 on Ubuntu 14.04 Our solution is to specify version 1.9.13 which passes the install. Looks like an npm ERR! [email protected] install: npm ERR! System Linux 3.16.7-tinycore64 |
Same here, 1.9.13 globally works. 1.9.16 doesn't. |
The issue, as originally reported, was fixed. I'm locking this issue to prevent this from becoming a dumping ground for a broad swath of unrelated issues. If you would like us to look into a particular issue you're having, please file a separate issue. |
Please see the error message below:
The text was updated successfully, but these errors were encountered: