1

Trying to install filebazaar on Ubuntu 18.04 and getting an error on the canvas module... anyone familiar with this issue? I've been all over node-canvas's github issues (such as this one where I left a comment), but none of the solutions are working for me so far.

Here's the command I'm running:

$ sudo npm install -g filebazaar

And here's the error output:

$ sudo npm install -g [email protected]

> [email protected] install /usr/local/lib/node_modules/canvas
> node-gyp rebuild

gyp ERR! configure error 
gyp ERR! stack Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/canvas/build'
gyp ERR! System Linux 4.15.0-55-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/canvas
gyp ERR! node -v v12.5.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok 
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/chris/.npm/_logs/2019-09-17T20_39_13_514Z-debug.log

Any assistance is appreciated :)

Improve this question

3 Answers 3

Reset to default
0

Maybe the directory doesnt have the proper rights, try this command sudo chmod 777

If it still doesnt work try these flag before your install sudo npm install -g --unsafe-perm

or sudo node-gyp rebuild -g --unsafe-perm

then try again

Improve this answer
3
  • Maybe the directory doesnt have the proper rights, try this command sudo chmod 777: Which directory are you referring to?
    – Chris Guida
    Commented Sep 18, 2019 at 20:29
  • /usr/local/lib/node_modules/canvas see this thread also stackoverflow.com/questions/42308879/npm-err-code-elifecycle
    – Saxtheowl
    Commented Sep 18, 2019 at 20:35
  • You're right, I didn't have permission on a number of directories, including /usr/local/lib/node_modules.
    – Chris Guida
    Commented Oct 8, 2019 at 16:01
0

I figured out the issue: there were some directories that were owned by root that needed to be owned by my user.

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.

Improve this answer
0

Configuring npm to install global packages to your user directory goes a long way to make these pesky permission issues go away.

See: https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally#manually-change-npms-default-directory

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.