Getting EACCESS and ELIFECYCLE errors trying to install on Ubuntu 18.04 about filebazaar

[shesek]

Thanks for the report. I updated to node-canvas v2 and published filebazaar v0.2.7. Can you check if this fixes the issue?

[chrisguida]

Still got the issue, although i think it may have been a permission issue on my end, I'm not sure.

I made myself owner of some npm-related folders, for instance:

sudo chown -R `whoami` /usr/local/lib/node_modules

...and that seems to have fixed the issue.

[chrisguida]

Is there any way I can try installing the old version to see if it works with my setup? Sorry, I'm kind of a newb at npm.

[chrisguida]

Well, I tried npm install [email protected] and now I'm having permission issues again :(

Now it's having trouble creating a symlink.

[chrisguida]

Okay, weird, next I tried

sudo npm install -g filebazaar

Which gave me the symlink permission issue and the ELIFECYCLE error again.

Tried npm install -g filebazaar again, just to see what the error was, and boom! No error.

I'm so confused.

[chrisguida]

Oh, I think I know what happened. I sudo rm'd the symlink, so now it doesn't need permission to overwrite the old symlink I think.

[chrisguida]

Okay never mind. I see what's happening.

I run npm install -g [email protected] and it gives me a "can't create symlink" EACCESS error, but not the ELIFECYCLE error. Perhaps this is because canvas is already installed properly from my earlier install of [email protected]?

Then I run sudo npm install -g [email protected] and I get an ELIFECYCLE error, but the symlink gets created. It doesn't appear to be pointing to anything, though, which makes it appear red in ls -al.

Then I run npm install -g [email protected] once again, and I get the ELIFECYCLE error.

Then I run npm install -g filebazaar to install 0.2.7, and the installation completes successfully.

So, yes, your update fixed the problem, but I also have some weird symlink creation problems. Is it best practice to chown /usr/local/bin to a non-root user?

[shesek]

What I would recommend is configuring npm to install global packages inside your home directory and adding that to your PATH. See instructions here. This typically resolves these pesky npm permission issues, which can indeed be a pain with how npm ships by default :(