Open HySoaKa opened 7 years ago
At one point, installing using sudo npm was bad. I don't know if this is still the case. Try using sudo -H
per this article: http://hood.ie/blog/why-you-shouldnt-use-sudo-with-npm.html
@parente Thank you for your answer. I didn't use sudo, I've tried to install the package with a root account.
In fact in the beginning I've tried to install jupyter-dashboards-server
using Ansible with a non root account. And seeing that it didn't work (and having a EACCESS error) I've tried to do it directly with the root account on the machine.
PS: I've tried sudo -H npm install jupyter-dashboards-server
with a user having root privileges, and it didn't work.
Hi. Were you able to find a solution to this? I am facing the exact same issue and have the same requirement of installing it as a root account.
Thanks.
@agapoorv The only solution that worked for me was to install it without the global option, specifying a prefix path with --prefix
option.
You will find more details here: https://docs.npmjs.com/files/folders#tl-dr
Hi,
I encountered a problem during installation of Jupyter Dashboard Server. Indeed, I've tried to install it globally with :
npm install -g jupyter-dashboards-server
knowing that I'm using root. And this is the error:As you can see above, I'm using:
And so, if I've understood correctly, the error is due to the
npm dedupe
. But oddly enough, when I've installed it locally, it worked like a charm. And annpm install -g jupyter-dashboards-server
puts executable files and man pages in the right directories.For me, technically a global installation is like a local installation with a certain prefix, and the link of the bin and man to the right dirs.
So why the
npm dedupe
didn't work with the global mode ?PS: I've assumed that this is an issue that affect Jupyter Dashboard Server.