ah yeah, i'm sure the console filling up with eaccess errors is fine
hey
i think maybe
npm is not actually a good way to distribute software
@catoutofbed I’ve been saying this for years!! (actually I said it once a week ago or whatever)
@catoutofbed there’s a workaround: cd into the node_modules directory and do a `sudo npm install` there (no `-g`)
@jordyd
i guess i'll have to go find the source of this and do that
@catoutofbed oh you’re not running npm directly? Is it some other installer?
@jordyd
oh i am
but they're not using it to distribute a library
they're using it to install an application
@catoutofbed yeah it will put binaries in node_modules/.bin
@jordyd
okay i'll try there
@catoutofbed I think most node people are running macOS where the dominant Homebrew package manager has “fixed” this issue by having /usr/local owned by the main user
@catoutofbed then symlink as appropriate
@jordyd
that sounds
awful
@catoutofbed oh yes, welcome to the world of Node
@catoutofbed trying to make this match the meter of "call me maybe" but it's not working 😞
@jamey
hey i just met you
and this is crazy
but installing software with npm
don't do it maybe
@catoutofbed recently I use Cargo. 😛
given that installing this just caused it to loop forever with EACCES errors
running as root
not sudo
as root