Closed plavjanik closed 2 years ago
This looks related to #180. There are some known workarounds:
sudo
and pass the --unsafe-perm
flag to npm install
(not ideal, may be necessary to change the permissions on the ~/.zowe
folder afterwards)Thank you for mentioning #180. I have tried both --unsafe-perm
and --ignore-scripts
. I am not sure what is the better option. Both options sound scary.
I have installed it as root because Node.js was installed under root and I wanted Zowe CLI to be installed globally. I will not use Zowe CLI as root but as a regular user.
--unsafe-perm
creates /root/.zowe
that is not what wanted. --ignore-scripts
that @dkelosky mentioned is closed to the behavior that I would expect. Ideally, I would like to see no errors (without any special option) when I am installing Zowe CLI to Node.js that was installed under root and no /root/.zowe
created since I will not run Zowe CLI as root.
Hi @plavjanik, someone else ran into this issue and we were able to resolve it by following this documentation: https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally
This issue has had no activity for 12 months. The issue also has less than 5 up-votes by the community. No action on this issue is targeted for the next 2 calendar quarters. Therefore, this issue is being closed. If you feel that this issue should continue to be available for community up-votes, you may reopen this issue.
Hello,
I have installed Node.js as root to
/opt/nodejs/node-v12.15.0-linux-s390x/
.I am trying to install Zowe CLI using commands:
The Zowe CLI is installed at the end but I am getting a lot of error messages. Are they false alarms or real problems?
The full log: