Recently, I made an attempt to install the memlab library from Meta's GitHub. Initially, when I installed it without using the -g flag, the installation was successful. However, I encountered an issue where I could not execute any of the memlab commands as I kept receiving an error stating that the memlab command could not be found.
Each time I tried running:
npm install -g memlab
I consistently received a series of errors:
npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /usr/local/lib/node_modules/memlab
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/memlab'
npm ERR! [Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/memlab'] {
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'mkdir',
npm ERR! path: '/usr/local/lib/node_modules/memlab'
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.
Even when attempting to use the command:
npm install -g memlab root/AdministratorI faced another set of errors:
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="97f0fee3d7f0fee3ffe2f5b9f4f8fa">[email protected]</a>/root/Administrator.git
npm ERR! <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="8deae4f9cdeae4f9e5f8efa3eee2e0">[email protected]</a>: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR! A complete log of this run can be found in: /Users/harshit4.dubey/.npm/_logs/2023-10-17T19_05_42_796Z-debug-0.log
I've been tirelessly searching for a solution to resolve this persistent error, but unfortunately, I have yet to find one.