on installing the phonegap i am getting an error
npm ERR! Window_NT 6.1. 7600
npm ERR! argv " C:\\Program File(x86)\\node.js\\node.exe" "C:\\Users\\Abuzar\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "phonegap"
npm ERR! node v4.4.3
npm ERR! npm v3.8.8
npm ERR! path C:\Users\Abuzar\AppData\Roaming\npm\node_modules\.staging
npm ERR! code EPERM
npm ERR! erryno -4048
npm ERR! syscall un link
npm ERR! Error:EPERM: operation not permitted, unlink 'C:\Users\Abuzar\AppData\Roaming\npm\node_modules\.stagging'
npm ERR! at Error <native>
npm ERR! { [Error: EPERM: operation not permitted, unlink 'C:\Users\Abuzar
\AppData\Roaming\npm\node_modules\.stagging']
npm ERR! errno: -4048,
npm ERR! syscall:'unlink',
npm ERR! path: 'C:\\Users\\AbuzaR\\AppData\\Roaming\\npm\\node_modules\\.stagging'
}
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Please include the following file with any support request:
npm ERR! C:\xampp\
htdocs\aa\npm-debug.log
Please help me here,
Had the same issue.
Deleting C:\Users\[User]\AppData\Roaming\npm\node_modules\.phonegap.DELETE fixed it for me.
Related
I just start learning react native. While installing expo npm install -g expo cli I'm getting that error. Can someone Tell me why?
npm ERR! code EPERM
npm ERR! syscall rename
npm ERR! path C:\Users\Lenovo\AppData\Roaming\npm\node_modules\expo-cli
npm ERR! dest C:\Users\Lenovo\AppData\Roaming\npm\node_modules\.expo-cli-DcNrljQz
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\Lenovo\AppData\Roaming\npm\node_modules\expo-cli' -> 'C:\Users\Lenovo\AppData\Roaming\npm\node_modules\.expo-cli-DcNrljQz'
npm ERR! [Error: EPERM: operation not permitted, rename 'C:\Users\Lenovo\AppData\Roaming\npm\node_modules\expo-cli' -> 'C:\Users\Lenovo\AppData\Roaming\npm\node_modules\.expo-cli-DcNrljQz'] {
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'rename',
npm ERR! path: 'C:\\Users\\Lenovo\\AppData\\Roaming\\npm\\node_modules\\expo-cli',
npm ERR! dest: 'C:\\Users\\Lenovo\\AppData\\Roaming\\npm\\node_modules\\.expo-cli-DcNrljQz'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
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! C:\Users\Lenovo\AppData\Local\npm-cache\_logs\2021-02-16T13_28_45_327Z-debug.log
I am using TFS source control and 2015 TFS Build Server.
I setup script to build on a build server. The first step is to clear the cache, because if not, it would randomly fail due to random error.
But now, almost half of the time it gives this new error:
2016-07-08T19:39:32.2041280Z > npm cache clean
2016-07-08T19:39:40.5819362Z npm ERR! Windows_NT 6.3.9600
2016-07-08T19:39:40.5819362Z npm ERR! argv "C:\\nodeJs\\node.exe" "C:\\nodeJs\\node_modules\\npm\\bin\\npm-cli.js" "cache" "clean"
2016-07-08T19:39:40.5819362Z npm ERR! node v4.4.7
2016-07-08T19:39:40.5819362Z npm ERR! npm v2.15.8
2016-07-08T19:39:40.5819362Z npm ERR! path C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\npm-cache
2016-07-08T19:39:40.5819362Z npm ERR! code EPERM
2016-07-08T19:39:40.5819362Z npm ERR! errno -4048
2016-07-08T19:39:40.5819362Z npm ERR! syscall rmdir
2016-07-08T19:39:40.6288231Z npm ERR! Error: EPERM: operation not permitted, rmdir 'C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\npm-cache'
2016-07-08T19:39:40.6288231Z npm ERR! at Error (native)
2016-07-08T19:39:40.6288231Z npm ERR! { [Error: EPERM: operation not permitted, rmdir 'C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\npm-cache']
2016-07-08T19:39:40.6288231Z npm ERR! errno: -4048,
2016-07-08T19:39:40.6288231Z npm ERR! code: 'EPERM',
2016-07-08T19:39:40.6288231Z npm ERR! syscall: 'rmdir',
2016-07-08T19:39:40.6288231Z npm ERR! path: 'C:\\Windows\\ServiceProfiles\\NetworkService\\AppData\\Roaming\\npm-cache' }
2016-07-08T19:39:40.6288231Z npm ERR!
2016-07-08T19:39:40.6288231Z npm ERR! Please try running this command again as root/Administrator.
2016-07-08T19:39:40.6757133Z npm ERR! Please include the following file with any support request:
2016-07-08T19:39:40.6757133Z npm ERR! C:\Work\9\s\Atlas.Prototype\src\starterproject\npm-debug.log
2016-07-08T19:39:40.7382460Z npm ERR! Windows_NT 6.3.9600
2016-07-08T19:39:40.7382460Z npm ERR! argv "C:\\nodeJs\\node.exe" "C:\\nodeJs\\node_modules\\npm\\bin\\npm-cli.js" "run" "cleancache"
2016-07-08T19:39:40.7382460Z npm ERR! node v4.4.7
2016-07-08T19:39:40.7382460Z npm ERR! npm v2.15.8
2016-07-08T19:39:40.7382460Z npm ERR! code ELIFECYCLE
2016-07-08T19:39:40.7382460Z npm ERR! angular2#5.0.4-v1.0.0 cleancache: `npm cache clean`
2016-07-08T19:39:40.7382460Z npm ERR! Exit status 4294963248
2016-07-08T19:39:40.7382460Z npm ERR!
2016-07-08T19:39:40.7382460Z npm ERR! Failed at the angular2#5.0.4-v1.0.0 cleancache script 'npm cache clean'.
2016-07-08T19:39:40.7382460Z npm ERR! This is most likely a problem with the angular2 package,
2016-07-08T19:39:40.7382460Z npm ERR! not with npm itself.
2016-07-08T19:39:40.7538723Z npm ERR! Tell the author that this fails on your system:
2016-07-08T19:39:40.7538723Z npm ERR! npm cache clean
How is it possible that it gives "permission" error when run, but when run again it succeeds, and if running again a 3rd time it is random?
What would be the steps to ensure npm cache clean is successful 100% of the time?
As the issue the random, it may not caused by permission.
Try to upgrade the npm to the latest version, to see whether the issue persists. Also, as #Christian.K mentioned, you may check if there is parallel build.
I've been trying to install nodemon using npm install -g nodemon, but I keep getting the following error. Please help
C:\Users\AllJs\Desktop\FF>npm install -g nodemon
npm ERR! tar.unpack untar error C:\Users\chris\AppData\Roaming\npm-cache\nodemon\1.9.1\package.tgz
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\AllJSAdmin\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "nodemon"
npm ERR! node v4.2.3
npm ERR! npm v2.13.1
npm ERR! path C:\Program Files\nodejs\node_modules\nodemon
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall mkdir
npm ERR! Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules\nodemon'
npm ERR! at Error (native)
npm ERR! { [Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules\nodemon']
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'mkdir',
npm ERR! path: 'C:\\Program Files\\nodejs\\node_modules\\nodemon',
npm ERR! fstream_type: 'Directory',
npm ERR! fstream_path: 'C:\\Program Files\\nodejs\\node_modules\\nodemon',
npm ERR! fstream_class: 'DirWriter',
npm ERR! fstream_stack:
npm ERR! [ 'C:\\Users\\AllJSAdmin\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\fstream\\lib\\dir-writer.js:35:25',
npm ERR! 'C:\\Users\\AllJSAdmin\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\mkdirp\\index.js:47:53',
npm ERR! 'FSReqWrap.oncomplete (fs.js:82:15)' ] }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\AllJS\Desktop\FF\npm-debug.log
You are not allowed to write to C:\Program Files\nodejs\node_modules\. Check your npm configuration, it should not be trying to store packages there.
Run npm config get prefix to determine the current npm folders prefix. On my Windows machine this will return something in the form:
C:\Users\<My Username>\AppData\Roaming\npm
which is a user writable location.
I am using vagrant to set up my enviroment, when I use sudo npm update, I get this error.
npm ERR! Linux 3.13.0-49-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "update"
npm ERR! node v0.12.2
npm ERR! npm v2.7.4
npm ERR! path ../mime/cli.js
npm ERR! code EPROTO
npm ERR! errno -71
npm ERR! EPROTO, symlink '../mime/cli.js'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Linux 3.13.0-49-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "update"
npm ERR! node v0.12.2
npm ERR! npm v2.7.4
npm ERR! path npm-debug.log.7dead0fa1a1d874805ab6e477bd46e0e
npm ERR! code ETXTBSY
npm ERR! errno -26
npm ERR! ETXTBSY, rename 'npm-debug.log.7dead0fa1a1d874805ab6e477bd46e0e'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! /vagrant/myapp/npm-debug.log
NOTE1: I am using trusty32 box also I am using node 0.12, npm 2.7.4 and mongodb 2.6.
NOTE2: I can not install mongoose and the default express-generator npm modules found in the package.json
UPDATE1: Npm error when i try "sudo npm install mongoose -save"
npm ERR! tar.unpack untar error /home/vagrant/.npm/wrappy/1.0.1/package.tgz
npm ERR! tar.unpack untar error /home/vagrant/.npm/brace-expansion/1.1.0/package
.tgz
npm ERR! Linux 3.13.0-49-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "mongoose"
npm ERR! node v0.12.2
npm ERR! npm v2.7.4
npm ERR! path /vagrant/myapp/node_modules/mongoose/node_modules/mongodb/node_mod
ules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_modules/node-pre-
gyp/node_modules/tar-pack/node_modules/fstream-ignore/node_modules/minimatch/tes
t/extglob-ending-with-state-char.js
npm ERR! code EPERM
npm ERR! errno -1
npm ERR! Error: EPERM, open '/vagrant/myapp/node_modules/mongoose/node_modules/m
ongodb/node_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_mo
dules/node-pre-gyp/node_modules/tar-pack/node_modules/fstream-ignore/node_module
s/minimatch/test/extglob-ending-with-state-char.js'
npm ERR! at Error (native)
npm ERR! { [Error: EPERM, open '/vagrant/myapp/node_modules/mongoose/node_modul
es/mongodb/node_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/nod
e_modules/node-pre-gyp/node_modules/tar-pack/node_modules/fstream-ignore/node_mo
dules/minimatch/test/extglob-ending-with-state-char.js']
npm ERR! errno: -1,
npm ERR! code: 'EPERM',
npm ERR! path: '/vagrant/myapp/node_modules/mongoose/node_modules/mongodb/node
_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_modules/node-
pre-gyp/node_modules/tar-pack/node_modules/fstream-ignore/node_modules/minimatch
/test/extglob-ending-with-state-char.js' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Linux 3.13.0-49-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "mongoose"
npm ERR! node v0.12.2
npm ERR! npm v2.7.4
npm ERR! path /vagrant/myapp/node_modules/mongoose/node_modules/mongodb/node_mod
ules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_modules/node-pre-
gyp/node_modules/npmlog/node_modules/are-we-there-yet/node_modules/readable-stre
am/lib/_stream_duplex.js
npm ERR! code EPERM
npm ERR! errno -1
npm ERR! Error: EPERM, open '/vagrant/myapp/node_modules/mongoose/node_modules/m
ongodb/node_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_mo
dules/node-pre-gyp/node_modules/npmlog/node_modules/are-we-there-yet/node_module
s/readable-stream/lib/_stream_duplex.js'
npm ERR! at Error (native)
npm ERR! { [Error: EPERM, open '/vagrant/myapp/node_modules/mongoose/node_modul
es/mongodb/node_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/nod
e_modules/node-pre-gyp/node_modules/npmlog/node_modules/are-we-there-yet/node_mo
dules/readable-stream/lib/_stream_duplex.js']
npm ERR! errno: -1,
npm ERR! code: 'EPERM',
npm ERR! path: '/vagrant/myapp/node_modules/mongoose/node_modules/mongodb/node
_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_modules/node-
pre-gyp/node_modules/npmlog/node_modules/are-we-there-yet/node_modules/readable-
stream/lib/_stream_duplex.js' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Linux 3.13.0-49-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "mongoose"
npm ERR! node v0.12.2
npm ERR! npm v2.7.4
npm ERR! path npm-debug.log.547bda60a6af6dbfaba7873fdc566e0c
npm ERR! code ETXTBSY
npm ERR! errno -26
npm ERR! ETXTBSY, rename 'npm-debug.log.547bda60a6af6dbfaba7873fdc566e0c'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Linux 3.13.0-49-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "mongoose"
npm ERR! node v0.12.2
npm ERR! npm v2.7.4
npm ERR! path /vagrant/myapp/node_modules/mongoose/node_modules/mongodb/node_mod
ules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_modules/node-pre-
gyp/node_modules/request/node_modules/combined-stream/node_modules/delayed-strea
m/lib/delayed_stream.js
npm ERR! code EPERM
npm ERR! errno -1
npm ERR! Error: EPERM, open '/vagrant/myapp/node_modules/mongoose/node_modules/m
ongodb/node_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_mo
dules/node-pre-gyp/node_modules/request/node_modules/combined-stream/node_module
s/delayed-stream/lib/delayed_stream.js'
npm ERR! at Error (native)
npm ERR! { [Error: EPERM, open '/vagrant/myapp/node_modules/mongoose/node_modul
es/mongodb/node_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/nod
e_modules/node-pre-gyp/node_modules/request/node_modules/combined-stream/node_mo
dules/delayed-stream/lib/delayed_stream.js']
npm ERR! errno: -1,
npm ERR! code: 'EPERM',
npm ERR! path: '/vagrant/myapp/node_modules/mongoose/node_modules/mongodb/node
_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_modules/node-
pre-gyp/node_modules/request/node_modules/combined-stream/node_modules/delayed-s
tream/lib/delayed_stream.js' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! tar.unpack untar error /home/vagrant/.npm/lodash._basetostring/3.0.0/pa
ckage.tgz
npm ERR! tar.unpack untar error /home/vagrant/.npm/lodash._createpadding/3.6.0/p
ackage.tgz
npm ERR! tar.unpack untar error /home/vagrant/.npm/lodash._createpadding/3.6.0/p
ackage.tgz
npm ERR! tar.unpack untar error /home/vagrant/.npm/lodash._createpadding/3.6.0/p
ackage.tgz
npm ERR! tar.unpack untar error /home/vagrant/.npm/lodash._basetostring/3.0.0/pa
ckage.tgz
npm ERR! tar.unpack untar error /home/vagrant/.npm/lodash._basetostring/3.0.0/pa
ckage.tgz
npm ERR! Linux 3.13.0-49-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "mongoose"
npm ERR! node v0.12.2
npm ERR! npm v2.7.4
npm ERR! path /vagrant/myapp/node_modules/mongoose/node_modules/mongodb/node_mod
ules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_modules/node-pre-
gyp/node_modules/request/node_modules/har-validator/node_modules/is-my-json-vali
d/test/json-schema.js
npm ERR! code EPERM
npm ERR! errno -1
npm ERR! Error: EPERM, open '/vagrant/myapp/node_modules/mongoose/node_modules/m
ongodb/node_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_mo
dules/node-pre-gyp/node_modules/request/node_modules/har-validator/node_modules/
is-my-json-valid/test/json-schema.js'
npm ERR! at Error (native)
npm ERR! { [Error: EPERM, open '/vagrant/myapp/node_modules/mongoose/node_modul
es/mongodb/node_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/nod
e_modules/node-pre-gyp/node_modules/request/node_modules/har-validator/node_modu
les/is-my-json-valid/test/json-schema.js']
npm ERR! errno: -1,
npm ERR! code: 'EPERM',
npm ERR! path: '/vagrant/myapp/node_modules/mongoose/node_modules/mongodb/node
_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_modules/node-
pre-gyp/node_modules/request/node_modules/har-validator/node_modules/is-my-json-
valid/test/json-schema.js' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Linux 3.13.0-49-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "mongoose"
npm ERR! node v0.12.2
npm ERR! npm v2.7.4
npm ERR! path /vagrant/myapp/node_modules/mongoose/node_modules/mongodb/node_mod
ules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_modules/node-pre-
gyp/node_modules/request/node_modules/har-validator/node_modules/bluebird/js/bro
wser/bluebird.min.js
npm ERR! code EPERM
npm ERR! errno -1
npm ERR! Error: EPERM, open '/vagrant/myapp/node_modules/mongoose/node_modules/m
ongodb/node_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_mo
dules/node-pre-gyp/node_modules/request/node_modules/har-validator/node_modules/
bluebird/js/browser/bluebird.min.js'
npm ERR! at Error (native)
npm ERR! { [Error: EPERM, open '/vagrant/myapp/node_modules/mongoose/node_modul
es/mongodb/node_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/nod
e_modules/node-pre-gyp/node_modules/request/node_modules/har-validator/node_modu
les/bluebird/js/browser/bluebird.min.js']
npm ERR! errno: -1,
npm ERR! code: 'EPERM',
npm ERR! path: '/vagrant/myapp/node_modules/mongoose/node_modules/mongodb/node
_modules/mongodb-core/node_modules/bson/node_modules/bson-ext/node_modules/node-
pre-gyp/node_modules/request/node_modules/har-validator/node_modules/bluebird/js
/browser/bluebird.min.js' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! tar.unpack untar error /home/vagrant/.npm/ansi-styles/2.0.1/package.tgz
npm ERR! tar.unpack untar error /home/vagrant/.npm/has-ansi/1.0.3/package.tgz
npm ERR! tar.unpack untar error /home/vagrant/.npm/strip-ansi/2.0.1/package.tgz
npm ERR! tar.unpack untar error /home/vagrant/.npm/escape-string-regexp/1.0.3/pa
ckage.tgz
npm ERR! tar.unpack untar error /home/vagrant/.npm/supports-color/1.3.1/package.
tgz
npm ERR! tar.unpack untar error /home/vagrant/.npm/graceful-readlink/1.0.1/packa
ge.tgz
npm ERR! Please include the following file with any support request:
npm ERR! /vagrant/myapp/npm-debug.log
UPDATE2: Switching to nvm works better with npm update but i cant not install mongoose i got the same error
UPDATE3: I think the problem is because the path
You are using an older version of NPM, the current latest version is 2.8.4 you are currently on 2.7.4. The release notes for 2.7.5 mention an issue with symbolic links that was fixed.
Updating NPM should fix this, run:
sudo npm install npm -g
There are two problems with using sudo with npm
99 problems like this.
It's a security issue.
The best solution is to use a node version manager. I use nvm. Another called n exists as well.
It felt like a couple steps "backwards" and I resisted it for a week or two, but making the switch was worth it.
NOTE: You should uninstall your "sudo" version of node.js, then install nvm as described on the github page.
Here 2.1.7 is the version you want to install.
sudo npm install -g npm#2.1.7
Am trying to install appium in ubuntu and got the below error.I searched so many articles and installed node through linuxbrew and even changed the permission also but still getting the below error.Can any one help please
npm ERR! tar.unpack untar error /home/ubuntu/.npm/appium/1.3.6/package.tgz
npm ERR! Linux 3.13.0-44-generic
npm ERR! argv "node" "/home/ubuntu/.linuxbrew/bin/npm" "install" "-g" "appium"
npm ERR! node v0.12.0
npm ERR! npm v2.5.1
npm ERR! path /home/ubuntu/lib/node_modules/appium
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! Error: EACCES, mkdir '/home/ubuntu/lib/node_modules/appium'
npm ERR! at Error (native)
npm ERR! { [Error: EACCES, mkdir '/home/ubuntu/lib/node_modules/appium']
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! path: '/home/ubuntu/lib/node_modules/appium',
npm ERR! fstream_type: 'Directory',
npm ERR! fstream_path: '/home/ubuntu/lib/node_modules/appium',
npm ERR! fstream_class: 'DirWriter',
npm ERR! fstream_stack:
npm ERR! [ '/home/ubuntu/.linuxbrew/lib/node_modules/npm/node_modules
/fstream/lib/dir-writer.js:36:23',
npm ERR! '/home/ubuntu/.linuxbrew/lib/node_modules/npm/node_modules/mkdirp/index.js:46:53',
npm ERR! 'FSReqWrap.oncomplete (fs.js:99:15)' ] }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Please include the following file with any support request:
npm ERR! /home/ubuntu/npm-debug.log
I have tried npm cache clean also but still not working.
What does linuxbrew doctor return?
Try to bash reset.sh --hardcore to completely reset Appium server and all npm modules