After 1 week break, I opened my pc again and when I want to 'expo start' from command window I get error like " 'expo' is not recognized as an internal or external command,operable program or batch file. " . And I tried to uninstall and install expo again and when I call " npm install --global expo-cli " I got this error.
npm ERR! code EPERM
npm ERR! syscall unlink
npm ERR! path C:\Users\tuna\AppData\Roaming\npm\node_modules\expo-cli\node_modules\#expo\.xdl.DELETE\binaries\windows\adb\AdbWinUsbApi.dll
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, unlink 'C:\Users\tuna\AppData\Roaming\npm\node_modules\expo-cli\node_modules\#expo\.xdl.DELETE\binaries\windows\adb\AdbWinUsbApi.dll'
npm ERR! [OperationalError: EPERM: operation not permitted, unlink 'C:\Users\tuna\AppData\Roaming\npm\node_modules\expo-cli\node_modules\#expo\.xdl.DELETE\binaries\windows\adb\AdbWinUsbApi.dll'] {
npm ERR! cause: [Error: EPERM: operation not permitted, unlink 'C:\Users\tuna\AppData\Roaming\npm\node_modules\expo-cli\node_modules\#expo\.xdl.DELETE\binaries\windows\adb\AdbWinUsbApi.dll'] {
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'unlink',
npm ERR! path: 'C:\\Users\\tuna\\AppData\\Roaming\\npm\\node_modules\\expo-cli\\node_modules\\#expo\\.xdl.DELETE\\binaries\\windows\\adb\\AdbWinUsbApi.dll'
npm ERR! },
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'unlink',
npm ERR! path: 'C:\\Users\\tuna\\AppData\\Roaming\\npm\\node_modules\\expo-cli\\node_modules\\#expo\\.xdl.DELETE\\binaries\\windows\\adb\\AdbWinUsbApi.dll',
npm ERR! parent: 'expo-cli'
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\tuna\AppData\Roaming\npm-cache\_logs\2020-10-03T15_36_23_690Z-debug.log
I couldnt find any solution that looks like my problem. Anybody has an idea to solve this problem.
Thanks in advance.
Related
~$ npm i puppeteer
npm ERR! code EPERM
npm ERR! syscall symlink
npm ERR! path ../extract-zip/cli.js
npm ERR! dest /storage/emulated/0/Android/data/io.spck.editor.node/files/Vision/node_modules/.bin/extract-zip
npm ERR! errno -1
npm ERR! Error: EPERM: operation not permitted, symlink '../extract-zip/cli.js' -> '/storage/emulated/0/Android/data/io.spck.editor.node/files/Vision/node_modules/.bin/extract-zip'
npm ERR! [Error: EPERM: operation not permitted, symlink '../extract-zip/cli.js' -> '/storage/emulated/0/Android/data/io.spck.editor.node/files/Vision/node_modules/.bin/extract-zip'] {
npm ERR! errno: -1,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'symlink',
npm ERR! path: '../extract-zip/cli.js',
npm ERR! dest: '/storage/emulated/0/Android/data/io.spck.editor.node/files/Vision/node_modules/.bin/extract-zip'
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.
This error shows up whenever I try to install packages like - Puppeteer, Nightmare & some more...
Kinda help me in this...
G:\angularProject\battingApp-update>npm i
npm ERR! code EPERM
npm ERR! syscall mkdir
npm ERR! path C:\Users\avtar~saini
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, mkdir 'C:\Users\avtar~saini'
npm ERR! [OperationalError: EPERM: operation not permitted, mkdir 'C:\Users\avtar~saini'] {
npm ERR! cause: [Error: EPERM: operation not permitted, mkdir 'C:\Users\avtar~saini'] {
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'mkdir',
npm ERR! path: 'C:\\Users\\avtar~saini'
npm ERR! },
npm ERR! isOperational: true,
npm ERR! stack: "Error: EPERM: operation not permitted, mkdir 'C:\\Users\\avtar~saini'",
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'mkdir',
npm ERR! path: 'C:\\Users\\avtar~saini'
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.
Looks like some permission issues.
First thing which you can do is run this command with administrative permissions.
If that doesn't work then You can try this with administrative permissions:
npm i --unsafe-perms
I think these should solve your problem
I have installed node on E dir and I am installing expo for react-native
E:>npm i -g expo-cli
npm ERR! code ETARGET
npm ERR! notarget No matching version found for semver#^7.3.5.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\jca\AppData\Local\npm-cache_logs\2021-05-03T05_32_28_520Z-debug.log
after this, when I am installing semver,
E:>npm install semver
npm ERR! code EPERM
npm ERR! syscall mkdir
npm ERR! path E:
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, mkdir 'E:'
npm ERR! [Error: EPERM: operation not permitted, mkdir 'E:'] {
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'mkdir',
npm ERR! path: 'E:\'
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.
Got the following error while executing npm install
node version 12.16.2
Running cmd as administrator
npm ERR! code EPERM
npm ERR! syscall unlink
npm ERR! path D:\Projects\BTP\Medical-Project\client\node_modules\.staging\npm-9e4fc1a9\man\man5\package-locks.5
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, unlink 'D:\Projects\BTP\Medical-Project\client\node_modules\.staging\npm-9e4fc1a9\man\man5\package-locks.5'
npm ERR! [OperationalError: EPERM: operation not permitted, unlink 'D:\Projects\BTP\Medical-Project\client\node_modules\.staging\npm-9e4fc1a9\man\man5\package-locks.5'] {
npm ERR! cause: [Error: EPERM: operation not permitted, unlink 'D:\Projects\BTP\Medical-Project\client\node_modules\.staging\npm-9e4fc1a9\man\man5\package-locks.5'] {
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'unlink',
npm ERR! path: 'D:\\Projects\\BTP\\Medical-Project\\client\\node_modules\\.staging\\npm-9e4fc1a9\\man\\man5\\package-locks.5'
npm ERR! },
npm ERR! stack: "Error: EPERM: operation not permitted, unlink 'D:\\Projects\\BTP\\Medical-Project\\client\\node_modules\\.staging\\npm-9e4fc1a9\\man\\man5\\package-locks.5'",
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'unlink',
npm ERR! path: 'D:\\Projects\\BTP\\Medical-Project\\client\\node_modules\\.staging\\npm-9e4fc1a9\\man\\man5\\package-locks.5',
npm ERR! parent: 'client'
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\kz\AppData\Roaming\npm-cache\_logs\2021-04-01T18_15_01_424Z-debug.log
I tried :
npm cache clean --force
deleted node_modules and installed again
disabled antivirus
Restarting laptop :)
I was able to fix this by
Closing any open prompts and editors eg. VSCode.
Opening the terminal or CMD as admin and running npm-install again.
I think the IDE is 'locking a file'.
C:\Users\Atanu>node -v
v10.16.0
C:\Users\Atanu>npm -v
6.9.0
C:\Users\Atanu>npm install -g newman
npm ERR! path C:\Program Files\Vbrick\nodejs\node_modules.staging
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall mkdir
npm ERR! Error: EPERM: operation not permitted, mkdir 'C:\Program Files\Vbrick\nodejs\node_modules.staging'
npm ERR! { [Error: EPERM: operation not permitted, mkdir 'C:\Program Files\Vbrick\nodejs\node_modules.staging']
npm ERR! cause:
npm ERR! { Error: EPERM: operation not permitted, mkdir 'C:\Program Files\Vbrick\nodejs\node_modules.staging'
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'mkdir',
npm ERR! path: 'C:\Program Files\Vbrick\nodejs\node_modules\.staging' },
npm ERR! stack:
npm ERR! 'Error: EPERM: operation not permitted, mkdir \'C:\Program Files\Vbrick\nodejs\node_modules\.staging\'',
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'mkdir',
npm ERR! path: 'C:\Program Files\Vbrick\nodejs\node_modules\.staging',
npm ERR! parent: 'newman' }
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 (though this is not recommended).
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Atanu\AppData\Roaming\npm-cache_logs\2020-02-20T06_37_27_595Z-debug.log
Try running the command prompt as admin.