Any recommendations on how to 'properly' setup the...
# sdf
d
Any recommendations on how to 'properly' setup the MacOS
Probably best to thread this question
p
let me see if i can google something, honestly it's a task i do every year and every time i do it, it has changed lol
d
Thanks @PabloZ
p
https://github.com/nvm-sh/nvm running
curl -o- <https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh> | bash
Should do the trick. then you can run nvm use 12, 13 or whatever, in your mac user instead of globally. That way you'll be saving permission headaches. After that you should run
nvm use 12
, try doing
which node
to see if it's using the /Users/{{yourname}}.nvm version In my case for example:
/Users/pzignani/.nvm/versions/node/v12.6.0/bin/node
(in the past, i have installed NVM through node itself... and through homebrew. These installations broke with time after mac updates changing permissions on /usr folders)
d
Thanks PabloZ. I did what you said and still am getting errors
Oh well
p
What's the output of
which node
?
d
/Users/darrenhill/.nvm/versions/node/v12.16.2/bin/node
p
and now when you run
npm install -g @oracle/suitecloud-cli
you get exactly the same error but with the new path?
a
The problem is purely the installation of npm on your machine. As many suggested here. Nothing with suitecloud. if you didnt manage to resolve the wirte permissions with npm on your machine you can try giving manually the write permissions to the folder it's complaining about. Not ideal but worth a try. cd into /usr/local/lib/node_modules
sudo chmod -R 777 @oracle
Or
sudo chmod -R +x @oracle