Open Hoekstraa opened 6 years ago
Apparently when I run chmod -R 777
on the build folder, it installs correctly. But this is a lot of effort to do if you need to install the library to lots of unique folders and just not safe. I think someone more knowledgeable about this project should look into this...
Where is the build folder you're referring to? I'm having this same problem on Ubuntu 16.04 and another package I'm trying to install depends on this one, so I'm currently unable to start a project because of this bug.
When you have the 'wd' folder, there's a build folder in there. Go to the wd folder, execute chmod 777 build
and then run npm install .
. That should work UNLESS the software you're installing installs wd again somewhere else. In that case you probably need to edit the make/install file to correct the fault. I hope this helps, @adueppen.
Is this in the /usr/local/bin/node_modules folder? It seems to be failing to create the wd directory. I'm trying to install it globally if that makes a difference.
Never mind, it turns out that I had been in the wrong node_modules folder.
Welp tried it in the right node_modules, but it's still refusing to install. Do I need to add the chmod 777 build to the install script?
You can run chmod -R 777 /usr/lib/node_modules/polymer-cli/node_modules/wd/build
in your case @adueppen. Sorry for the delayed response.
When trying to install the latest version of wd from npm with 'npm install wd' I get the following error: https://pastebin.com/erxKzBXL
I don't see more info in the logfile. OS is
FreeBSD 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 02:08:28 UTC 2017 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
EDIT: It seems to be a different error then #509 because that fix doesn't change anything for me, it also doesn't matter what user(root/personal/sudo) I am.
How can this error be circumvented A.S.A.P.?