Getting EACCES setting up Plasmic

Developer Support
1

npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /usr/local/lib/node_modules/@plasmicapp
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, mkdir ‘/usr/local/lib/node_modules/@plasmicapp’
npm ERR! [Error: EACCES: permission denied, mkdir ‘/usr/local/lib/node_modules/@plasmicapp’] {
npm ERR! errno: -13,
npm ERR! code: ‘EACCES’,
npm ERR! syscall: ‘mkdir’,
npm ERR! path: ‘/usr/local/lib/node_modules/@plasmicapp’
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/peterquinn/.npm/_logs/2022-10-03T21_35_57_837Z-debug-0.log

anyone know why I am getting this error

all I tried to do was add globaly

2

Yes, the current user in the terminal who is running the command does not have access to the package.

prefixing your command with sudo will fix the issue

But I am also wondering, why install globally and not on a project level?

As a general rule, globally installed packages are bad practice unless you need to access the binary at a root level. Most of the time this is not the case

3

Ok , I fixed that but now I am getting issues syncing my project

4

after getting it auth