UPDATE See this answer for a better way.
You must set the correct permissions (ownership) so that npm can access your (under) directories with your normal user permissions:
sudo chown -R $USER <directory>
where in your case <directory> is /home/me and -R is for recursive, to also change ownership of all your subdirectories, which is exactly what you want. This should fix the EACCESS problem.
Unfortunately, the tip for running the root/Administrator command is wrong here.
You want to avoid running npm with sudo ever since recommended by the creator of npm Isaac Schlüter :
I highly recommend that you do not do package management with sudo! Arbitrary scripts can be executed in packages, which makes the package manager’s team safe, like cutting a chainsaw. Of course, he’s quickly and definitely going to overcome any obstacles, but you really may need an obstacle to stay there.
See here for more details .
Dmitri Zaitsev Apr 22 '15 at 4:45 2015-04-22 04:45
source share